Security
Encryption and transmission
Encryption and transmission
All data is encrypted in transit using TLS 1.2 or higher and at rest using AES-256. Credentials are stored using AWS KMS. Infrastructure is hosted on AWS and provisioned via Infrastructure-as-Code with least-privilege IAM roles. Access to production systems is controlled, logged, and protected with MFA.
Internal practices
Internal practices
- Background checks are conducted for all employees
- Employees receive regular security training
- Endpoint protection and device management enforced via MDM
- Regular penetration testing and third-party audits
- Customer data is never entered into external AI tools by employees
SOC 2 Type II
SOC 2 Type II
Antimetal is SOC 2 Type II certified. Our controls and procedures have been independently audited and validated to meet industry standards for security, availability, and confidentiality.Contact security@antimetal.com for a copy of the report.
HIPAA
HIPAA
Antimetal is HIPAA compliant. Protected health information is handled in accordance with HIPAA requirements. Contact security@antimetal.com for details.
Vulnerability disclosure
Vulnerability disclosure
Report security concerns to security@antimetal.com.
Privacy and Data
Data isolation
Data isolation
All tenant data runs in isolated environments with strict separation boundaries. There is no cross-contamination between customers. Lightweight metadata such as alert identifiers and investigation status may be temporarily retained for tracking purposes.
AI providers and model usage
AI providers and model usage
Antimetal uses third-party AI APIs from Anthropic, OpenAI, and Google. All providers are configured with no-data-retention policies. Customer data is never used to train shared or generalized models. Each customer’s data is handled in a segregated environment with multi-tenant isolation controls.
AI in the product
AI in the product
AI accelerates root cause analysis and generates remediation recommendations tied to evidence. All AI outputs are linked to underlying data so customers can validate results independently. Audit logs capture all AI-assisted activity. AI augments investigation quality but never operates outside customer visibility.
Integration Permissions
Each integration requests only the minimum permissions needed. See the individual integration pages for details on specific scopes and access levels.Slack
Minimal OAuth scopes, no message persistence
GitHub
Repository access, pull requests, CI/CD monitoring
CloudWatch
Read-only IAM Role via CloudFormation
GCP
Read-only service account across projects
Datadog
Read-only API and Application keys
Grafana Cloud
Read-only access policy token
Sentry
Read-only internal integration token
PagerDuty
Read-only User API Token
Incident.io
Read-only API key
Best Practices
Review AI outputs
Review AI outputs
Antimetal surfaces recommendations tied to evidence. Review them before acting. All recommendations include links to the underlying data so you can verify independently.
Manage credentials securely
Manage credentials securely
Use the Antimetal dashboard to store integration credentials. Do not share API keys over Slack or email.
Use least-privilege access
Use least-privilege access
When possible, scope integration permissions to specific projects, repositories, or environments. Each integration page documents the minimum required permissions.