Skip to content
    Compliance & Security

    Compliance Framework Reference

    The full list of compliance frameworks SeqOps scans against, by cloud provider and for servers.

    These are the frameworks SeqOps scans a customer's environment against. They are not a claim that SeqOps itself holds certification to any of them — see SeqOps Information Security & Compliance Approach.

    How Frameworks Work in Your Plan

    • •SeqOps has four catalogs: AWS, Azure, GCP, and Server Compliance — 55 entries in total.
    • •Every framework is off by default. You switch frameworks on or off under Compliance → Library.
    • •Each plan includes a set number of compliance frameworks: one on Core, three on Edge, and six on Max. For partner customers, Max+ includes nine. The catalogs below show what SeqOps generally supports; your findings map against the frameworks selected for your package.
    • •One framework is one standard, such as CIS, ISO 27001 or NIS2, on every cloud and version, so CIS on AWS, Azure and GCP counts as one framework against your plan. The number after each catalog heading counts entries (versions), not frameworks.
    • •Versions marked legacy have been superseded by their publisher. They still work and still score, and the library shows a Legacy label next to them. See Moving to a Newer Version below.

    What a Score Covers

    SeqOps checks the technical configuration of your environment. For regulations and laws — GDPR, HIPAA, NIS2, GxP 21 CFR Part 11 and GxP EU Annex 11 — that covers only their technical requirements, such as encryption, access control and logging. A passing score for one of these means the technical controls SeqOps can check are in place. It doesn't mean your organisation complies with the law, which also depends on policies, contracts and processes that a scan can't see.

    AWS Compliance Library (25)

    • •CIS — 1.4, 1.5, 2.0, 3.0, 4.0.1
    • •CISA
    • •ENS — RD2022
    • •FedRAMP-Low — Rev. 4 (legacy: FedRAMP now uses Rev. 5 baselines, not yet in the catalog)
    • •FedRAMP-Moderate — Rev. 4 (legacy: FedRAMP now uses Rev. 5 baselines, not yet in the catalog)
    • •FFIEC
    • •GDPR
    • •GxP-21-CFR-Part-11
    • •GxP-EU-Annex-11
    • •HIPAA
    • •ISO27001 — 2013 (legacy: use 2022), 2022
    • •MITRE-ATTACK
    • •NIST-800-171 — Rev. 2 (legacy: Rev. 3 not yet in the catalog)
    • •NIST-800-53 — Rev. 4 (legacy: use Rev. 5), Rev. 5
    • •NIST-CSF — 1.1 (legacy: 2.0 not yet in the catalog)
    • •PCI — 3.2.1 (legacy: use 4.0), 4.0
    • •RBI-Cyber-Security-Framework
    • •SOC2

    Azure Compliance Library (12)

    • •C5 — 2025
    • •CCC
    • •CIS Azure Foundations Benchmark — 2.0, 2.1, 3.0, 4.0
    • •ENS — RD2022
    • •ISO27001 — 2022
    • •MITRE-ATTACK
    • •NIS2
    • •PCI — 4.0
    • •SOC2

    GCP Compliance Library (5)

    Four frameworks, five entries: CIS has two versions.

    • •CIS GCP Foundations Benchmark — 2.0, 3.0
    • •ENS — RD2022
    • •MITRE-ATTACK
    • •PCI — 4.0

    Server Compliance (13)

    On servers, these names are tags on the checks of the OS hardening profile you switch on, rather than frameworks you switch on one by one.

    • •CIS Benchmarks
    • •CIS Controls v7
    • •CIS Controls v8
    • •CMMC v2.0
    • •GDPR
    • •Gpg13
    • •HIPAA
    • •ISO 27001:2013 (legacy — server checks aren't tagged for ISO 27001:2022 yet)
    • •Mitre Techniques
    • •NIST 800-53
    • •PCI DSS
    • •SOC 2
    • •TSC — the AICPA Trust Services Criteria that SOC 2 reports are written against. Checks tagged TSC and SOC 2 overlap; they're listed separately because the hardening profile tags them separately.

    CIS Controls v7 is listed for older profiles; CIS Controls v8 replaced it.

    Moving to a Newer Version

    A new version is a separate entry with its own score, so switching doesn't carry your old score across.

    1. Go to Compliance → Library and find the newer version, for example PCI 4.0 next to PCI 3.2.1.
    2. If you're at your plan's framework limit, switch the legacy version off first. Switching it off frees its place on your plan.
    3. Switch the newer version on.
    4. Run a scan, or wait for the next scheduled one. The new version scores from that scan, and its trend starts there.
    5. Expect a different score. Newer versions add and change controls, so the same environment can score differently.

    If you need both versions while an audit finishes, keep both on; each counts toward your plan.

    Related

    For how scores are calculated against your framework, see Understanding SeqOps Compliance Scores.

    complianceframeworksreferenceawsazuregcpservercatalog

    We use cookies

    We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy