@@ -38,16 +38,16 @@ Any repo (model or dataset) stored in a non-default location will display its Re
## Regulatory and legal compliance
-In regulated industries, companies may be required to store data in a specific region.
+Regulated industries often require data storage in specific regions.
-For companies in the EU, that means you can use the Hub to build ML in a GDPR compliant way: with datasets, models and inference endpoints all stored within EU data centers.
+For EU companies, you can use the Hub for ML development in a GDPR-compliant manner, with datasets, models and inference endpoints stored in EU data centers.
## Performance
-Storing your models or your datasets closer to your team and infrastructure also means significantly improved performance, for both uploads and downloads.
+Storing models and datasets closer to your team and infrastructure significantly improves performance for both uploads and downloads.
-This makes a big difference considering model weights and dataset files are usually very large.
+This impact is substantial given the typically large size of model weights and dataset files.
-As an example, if you are located in Europe and store your repositories in the EU region, you can expect to see ~4-5x faster upload and download speeds vs. if they were stored in the US.
+For example, European users storing repositories in the EU region can expect approximately 4-5x faster upload and download speeds compared to US storage.
-
+## Accessing Audit Logs
+
+Audit Logs are accessible through your organization settings. Each log entry includes:
+
+- Who performed the action
+- What type of action was taken
+- A description of the change
+- Location and anonymized IP address
+- Date and time of the action
+
+You can also download the complete audit log as a JSON file for further analysis.
+
+## What Events Are Tracked?
+
+### Organization Management & Security
+
+- Core organization changes
+ - Creation, deletion, and restoration
+ - Name changes and settings updates
+- Security management
+ - Security token rotation
+ - Token approval system (enabling/disabling, authorization requests, approvals, denials, revocations)
+ - SSO events (logins and joins)
+
+### Membership and Access Control
+
+- Member lifecycle
+ - Invitations (sending, accepting) and automatic joins
+ - Adding and removing members
+ - Role changes and departures
+- Join settings
+ - Domain-based access
+ - Automatic join configurations
+
+### Content and Resource Management
+
+- Repository administration
+ - Core actions (creation, deletion, moving, duplication)
+ - Settings and configuration changes
+ - Enabling/disabling repositories
+ - DOI management
+ - Resource group assignments
+- Collections
+ - Creation and deletion events
+- Repository security
+ - Secrets management (individual and bulk)
+ - Variables handling (individual and bulk)
+- Spaces configuration
+ - Storage modifications
+ - Hardware settings
+ - Sleep time adjustments
+
+### Billing and AWS Integration
+
+- Payment management
+ - Payment methods (adding/removing)
+ - Customer account creation
+ - AWS integration setup and removal
+- Subscription lifecycle
+ - Starting and renewing
+ - Updates and cancellations
+ - Cancellation reversals
+
+### Resource Groups
+
+- Administrative actions
+ - Creation and deletion
+ - Settings modifications
+- Member management
+ - Adding and removing users
+ - Role assignments and changes
diff --git a/docs/hub/enterprise-hub-advanced-security.md b/docs/hub/enterprise-hub-advanced-security.md
new file mode 100644
index 000000000..8dcdc3b87
--- /dev/null
+++ b/docs/hub/enterprise-hub-advanced-security.md
@@ -0,0 +1,29 @@
+# Advanced Security
+
+<Tip warning={true}>
+This feature is part of the <a href=){kind=link}
+ 
+