Mitigant FAQs

How often can we run validations?

‍

CSPM/KSPM (Continuous):

• Always-on monitoring
• Real-time detection of changes
• Immediate alerts for new issues
• No manual triggering required

‍

CAE (Flexible Scheduling):

• Automated Scheduling: Use Attack Scheduler for recurring campaigns (daily, weekly, custom intervals)
• On-Demand Execution: Run attacks anytime with button clicks
• Continuous Validation: Aligns with CTEM (Continuous Threat Exposure Management) methodology

‍

Perfect for:

• After deploying new security controls (CAE)
• During security gamedays (CAE)
• When responding to new threat intelligence (CAE)
• For compliance audits (all products)
• Post-incident validation that remediation worked (CAE + CSPM)

This continuous/flexible approach contrasts sharply with annual penetration tests-you get ongoing assurance instead of point-in-time validation.

‍

Do you support custom scenarios and policies?

Yes, across all products:

‍

CAE - Custom Attack Scenarios:

• Attack Builder: Create custom cloud attacks in seconds without writing code using our intuitive interface
• Cloud Attack Language (CAL): YAML-based schema for constructing complex, multi-step attacks
• Attack-as-Code: Build custom detection validation into Detection-as-Code workflows
• API-driven construction: Combine available attack actions into custom sequences
• Threat Intelligence Integration: Create scenarios based on specific CTI feeds
• Tabletop Exercise Implementation: Convert threat modeling into executable attacks
• Mitigant Threat Catalog: Free, interactive resource with executable CLI commands and CAL definitions for MITRE ATT&CK cloud techniques

Learn more: Mitigant Attack Builder
Learn more: Mitigant Threat Catalog
Visit: Mitigant Threat Catalog

‍

CSPM - Custom Policies:

• Define organization-specific security requirements
• Create custom compliance frameworks
• Set thresholds and severity levels
• Build policy exceptions for approved deviations

‍

KSPM - Custom Benchmarks:

• Define Kubernetes security standards for your organization
• Create pod security policies aligned with your architecture
• Set namespace-specific requirements

‍

What frameworks does the Mitigant Platform align with?

Attack Frameworks (CAE):

• MITRE ATT&CK for Enterprise: All cloud attack techniques mapped
• MITRE ATLAS: AI/ML security techniques for GenAI workloads
• Cloud and AI attack techniques mapped across both frameworks, expanded as new techniques emerge

‍

Compliance Frameworks (CSPM/KSPM):

• ISO 27001
• SOC 2
• HIPAA
• PCI-DSS
• BSI C5 (German cloud security standard)
• NIST 800-53
• NIS2 Directive (European cybersecurity requirements)
• DORA (Digital Operational Resilience Act)
• ENISA SME (European cybersecurity for small/medium enterprises)
• AWS Foundational Security Best Practices
• AWS Well-Architected Framework (WAF)
• CIS Benchmarks for AWS, Azure, GCP, and Kubernetes
• GDPR considerations

‍

Security Methodologies (All Products):

• CTEM (Continuous Threat Exposure Management): Aligns with Gartner's methodology
• Adversarial Exposure Validation (AEV): Prove which exposures are actually exploitable before prioritizing remediation
• Threat-Informed Defense: Use threat intelligence to prioritize security investments

‍

See platform details: Cloud Attack Emulation Platform

‍