Understanding SeqOps Compliance Scores
How SeqOps calculates compliance scores and what they represent.
Compliance scores show how your environment aligns with the selected framework based on the controls analyzed by SeqOps. SeqOps helps teams understand their compliance posture and identify gaps against selected frameworks.
Compliance scores should be used as a practical indicator of framework alignment and control performance, not as a substitute for an external audit or formal assessment.
What the Score Represents
The compliance score reflects the result of the controls evaluated within the selected framework. A higher score generally means that more evaluated controls align with the selected framework. The score is based on the controls and findings evaluated across connected cloud environments and monitored servers.
What the Score Does Not Mean
A compliance score does not represent certification or formal regulatory approval. It is a measurement based on the controls and findings evaluated by the SeqOps platform.
How the Score Is Calculated
Scores are calculated by evaluating each control against your actual configuration:
- •Pass — Control is properly implemented
- •Fail — Control is missing or misconfigured
- •N/A — Control is not applicable to your environment
Frameworks Considered
SeqOps scans your environment against four catalogs of frameworks:
- •AWS Compliance Library — 25 entries
- •Azure Compliance Library — 12 entries
- •GCP Compliance Library — 5 entries
- •Server Compliance — 13 entries
That is 55 entries in total. For the full list per catalog, see the Compliance Framework Reference. Your plan includes a set number of compliance frameworks (one on Core, three on Edge, five on Max), and your score is calculated against the frameworks you select.
These are frameworks SeqOps scans your environment against. A score against a framework is not a certification of your environment, and it does not mean SeqOps itself holds that certification. For how SeqOps approaches its own security, see SeqOps Information Security & Compliance Approach.
What Affects the Score
Common factors include:
- •Failed controls
- •Missing required configurations
- •Detected configuration risks
- •Changes in connected environments or monitored servers
How to Improve the Score
To improve the score:
- •Review failed controls
- •Investigate affected resources
- •Apply the recommended remediation guidance
- •Re-run or wait for the next analysis cycle
Compliance scores are updated based on the latest analysis results available in the platform.