Skip to main content

Understanding Compliance Frameworks in DSALTA

Learn what compliance frameworks are, how they work in DSALTA, and how to choose the right frameworks for your organization.

John Ozdemir avatar
Written by John Ozdemir
Updated over a month ago

Compliance frameworks provide structured sets of security and privacy requirements that organizations must meet to achieve certification. DSALTA supports multiple frameworks, allowing you to manage all your compliance needs in one platform.

What Are Compliance Frameworks?

A compliance framework is a structured set of guidelines, controls, and best practices designed to ensure organizations meet specific security, privacy, or regulatory requirements. Each framework serves different purposes and audiences:

Industry Standards: Demonstrate security practices to customers and partners (SOC 2, ISO 27001) Regulatory Compliance: Meet legal requirements for specific industries or regions (HIPAA, GDPR) Security Benchmarks: Implement recognized security controls (CIS, NIST)

Frameworks Available in DSALTA

DSALTA supports 15+ compliance frameworks across different categories:

Security & Trust Frameworks

SOC 2: The most common framework for SaaS companies, focused on security, availability, processing integrity, confidentiality, and privacy. Required by many enterprise customers.

ISO 27001: International standard for information security management systems. Recognized globally and often required for international business.

ISO 27017: Cloud-specific extension of ISO 27001, focusing on cloud service security.

ISO 27018: Privacy controls for cloud computing, particularly relevant for organizations handling personal data in the cloud.

Privacy & Data Protection

GDPR: European Union regulation for data privacy and protection. Required for any organization handling EU residents' data.

CCPA/CPRA: California privacy regulations. Relevant for businesses serving California residents.

HIPAA: Healthcare privacy and security requirements for organizations handling protected health information.

Financial & Payment Security

PCI DSS: Payment card industry security standards for organizations handling credit card data.

SOX: Financial reporting controls, primarily for publicly traded companies.

Government & Sector-Specific

FedRAMP: Required for cloud services used by US federal agencies.

NIST CSF: Cybersecurity framework widely used by government contractors and critical infrastructure.

NIST AI RMF: Risk management framework for artificial intelligence systems.

CMMC: Cybersecurity maturity model certification required for Department of Defense contractors.

Industry-Specific Standards

CIS Controls: Center for Internet Security's prioritized security actions.

TISAX: Automotive industry information security assessment.

23 NYCRR 500: New York financial services cybersecurity regulation.

[Screenshot needed: Frameworks page showing available frameworks with categories]

How Frameworks Work in DSALTA

Each framework in DSALTA consists of:

Controls: Specific security requirements you must implement (e.g., "Multi-factor authentication is required")

Evidence Requirements: Documentation or proof needed to demonstrate control implementation

Tests: Automated checks that verify controls are working correctly

Policies: Written procedures and standards that document your approach

Audit Criteria: Specific elements auditors will evaluate during certification

Framework Relationships and Overlap

Many frameworks share similar requirements. For example:

  • Access control requirements appear in SOC 2, ISO 27001, HIPAA, and GDPR

  • Encryption requirements are common across most frameworks

  • Incident response procedures are nearly universal

DSALTA's intelligent mapping recognizes these overlaps. When you implement a control for SOC 2, DSALTA automatically:

  • Maps it to equivalent controls in other active frameworks

  • Reuses evidence across multiple frameworks

  • Shows which frameworks each control satisfies

This means implementing your second framework requires significantly less work than your first.

Framework Progress Tracking

For each active framework, DSALTA displays:

Completion Percentage: Overall progress toward full implementation

Control Status Breakdown: How many controls are completed, in progress, or not started

Evidence Completeness: Percentage of required evidence collected

Test Results: Automated test pass/fail rates

Readiness Score: Assessment of audit readiness

These metrics help you understand where you stand and what needs attention.

Framework Recommendations

When you first access the Frameworks page, DSALTA provides personalized recommendations based on:

  • Your industry and business model

  • Organization size and maturity

  • Geographic location and data handling

  • Customer requirements (if indicated)

Recommended frameworks appear with a "Recommended" badge, but you can explore and activate any framework regardless of recommendations.

Certification vs. Compliance

Understanding the difference:

Compliance: Meeting framework requirements and having evidence to prove it. You can be compliant without formal certification.

Certification: Official attestation from a third-party auditor that you meet framework requirements. Required for many customer contracts.

DSALTA helps you achieve both. Use the platform to become compliant, then engage an auditor when you're ready for formal certification.

Choosing Your Frameworks

Consider these factors when selecting frameworks:

Customer Requirements: What do your customers require in security questionnaires or contracts?

Industry Standards: What's expected in your industry? (SaaS companies typically start with SOC 2)

Geographic Scope: Do you serve customers in specific regions? (EU = GDPR, California = CCPA)

Regulatory Obligations: Are you in a regulated industry? (Healthcare = HIPAA, Finance = SOX/PCI)

Business Goals: Are you pursuing government contracts (FedRAMP) or international expansion (ISO 27001)?

Multi-Framework Strategy

Most organizations implement multiple frameworks over time:

Year 1: SOC 2 (customer requirement) + GDPR (EU customers)

Year 2: Add ISO 27001 (international expansion)

Year 3: Add industry-specific frameworks as needed

DSALTA's overlapping control mapping makes this progression efficient—each additional framework builds on previous work.

Framework Lifecycle

Frameworks aren't one-time achievements:

Initial Implementation: 3-6 months to first certification

Continuous Compliance: Ongoing monitoring and evidence collection

Annual Audits: Yearly recertification to maintain credentials

Framework Updates: Periodic standard updates requiring control adjustments

DSALTA supports you through the entire lifecycle, not just initial certification.

Did this answer your question?