Enterprise Features¶
Experimental
Enterprise features are early-stage and should be considered experimental. APIs and configuration formats may change.
Policy Backends¶
OPA/Rego¶
Delegate policy decisions to Open Policy Agent using Rego policies.
Cedar¶
Use AWS Cedar for fine-grained, RBAC-style policy decisions.
policy_backend: cedar
cedar:
policy_path: /path/to/cloneguard.cedar
entities_path: /path/to/entities.json
SIEM Connectors¶
Forward audit events to your security information and event management platform.
Splunk HEC¶
siem:
backend: splunk
splunk:
hec_url: "https://splunk.example.com:8088"
token_env: "SPLUNK_HEC_TOKEN"
index: "ai_security"
source_type: "cloneguard"
Microsoft Sentinel¶
siem:
backend: sentinel
sentinel:
dcr_endpoint: "https://dcr.monitor.azure.com"
dcr_id: "dcr-..."
stream_name: "Custom-CloneGuard_CL"
Google Chronicle¶
Agent Identity (SPIFFE)¶
Inject verified agent identity into audit events for multi-agent correlation.
Audit events will include the agent's SPIFFE ID
(spiffe://trust-domain/agent/name).
Fleet Deployment¶
Ansible¶
An Ansible role is included for deploying CloneGuard across a fleet of developer workstations.
MDM (macOS)¶
Configuration profiles are available for Jamf Pro and Microsoft Intune to deploy CloneGuard policy via MDM on macOS.