SOC 2 (Trust Services Criteria)
Attestkeep maps what your cluster's admission control and image scanning recorded in a period to 13 clauses of AICPA TSP section 100 (2017, revised 2022). 11 are assessed from those records; 2 are marked outside scope, each with the reason.
11 clauses a cluster can answer.
Citations and titles as the report prints them. Open a clause to read what it asks, restated close to the instrument's own words.
Trust Services Criteria
AICPA TSP section 100 (2017, revised 2022)
Common Criteria CC6–CC9 and Availability A1
| Citation | Clause | Report sections |
|---|---|---|
| CC4.1 |
Evaluations to ascertain that controls are present and functioningThe entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning. |
Admission decisionsAvailability |
| CC6.1 |
Logical access security over protected information assetsThe entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives. |
Control statementEvidence chain |
| CC6.6 |
Logical access measures against threats from outside the system boundaryThe entity implements logical access security measures to protect against threats from sources outside its system boundaries. |
Control statementSupply chain |
| CC6.8 |
Prevent or detect the introduction of unauthorised or malicious softwareThe entity implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software to meet the entity's objectives. |
Admission decisionsSupply chain |
| CC7.1 |
Detect configuration changes and newly discovered vulnerabilitiesThe entity uses detection and monitoring procedures to identify changes to configurations that result in the introduction of new vulnerabilities, and susceptibilities to newly discovered vulnerabilities. |
Coverage |
| CC7.2 |
Monitor components for anomalies indicative of malicious actsThe entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives. |
Evidence chain |
| CC7.3 |
Evaluate security events to determine whether they are incidentsThe entity evaluates security events to determine whether they could or have resulted in a failure to meet its objectives and, if so, takes actions to prevent or address such failures. |
Admission decisionsTriage decisions |
| CC7.4 |
Respond to identified security incidentsThe entity responds to identified security incidents by executing a defined incident response program to understand, contain, remediate, and communicate security incidents, as appropriate. |
Admission decisionsBreak-glass events |
| CC8.1 |
Change managementThe entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives. |
Admission decisionsControl statement |
| CC9.2 |
Vendor and business partner riskThe entity assesses and manages risks associated with vendors and business partners. |
Supply chainControl statement |
| A1.2 |
Recovery infrastructure and availability of the controlThe entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data backup processes, and recovery infrastructure to meet its objectives. |
Availability |
2 clauses marked outside scope, and why
| Citation | Clause and reason |
|---|---|
| CC1.1 – CC1.5 | Control environment the control environment concerns people, governance and accountability. No cluster control observes it. |
| CC3.1 – CC3.4 | Risk assessment the entity's risk assessment is a document and a process. The thresholds and remediation windows reproduced in the control statement are one output of it, not the assessment itself. |
Evidence from records the cluster already keeps.
Nothing is filled in by hand. Each clause's answer carries a status (met, partial, gap or outside scope), a note with the period's own numbers, and the report sections those numbers come from.
Each SOC 2 clause is assessed by a rule of its own, written for that clause, against the report sections below.
What the report contains.
Every package carries the same sections, whatever the framework. The ones marked are those SOC 2 answers cite, with the number of clauses citing each.
- Organisation
- Framework mapping
- Cluster
- Control statement4
- Coverage1
- Vulnerability findings
- Outcomes
- Admission decisions5
- Supply chain3
- Triage decisions1
- Break-glass events1
- Availability2
- Evidence chain2
- Deployment context
- Issues
- Ledger
- Population
- Runtime events
- Producer statements (VEX)
The scope paragraph, as the report states it.
This document reports what one Kubernetes cluster's admission control and image scanning recorded during the period, mapped onto the Trust Services Criteria. It is evidence for an audit, not an audit: only a service auditor issues an opinion, and only the entity defines its own system boundary. The criteria below are the ones a container image control speaks to; the control environment, risk assessment and monitoring criteria that concern the entity as a whole are listed where this control is one input to them, and marked outside_scope where it is not an input at all.
About SOC 2 and Attestkeep
Is this a SOC 2 certification?
No. The package is evidence produced from your cluster's own records. It is not a certification, and no auditor is obliged to accept it. The scope paragraph on this page is the one the report itself carries.
Why are 2 of the clauses outside scope?
They ask about things one cluster's admission and scanning records cannot show. They are listed with the reason rather than left out, so whoever reads the report can see the gap is deliberate.
Which plan includes SOC 2?
Every plan can report against it. Community and Team include one framework of your choice, Business three, Enterprise every one. Prices are on the pricing page.
How does an auditor check the package?
In a browser at attestkeep.com/verify.html, where nothing is uploaded, or with the short script on the documentation site. Neither needs us. For auditors has the details.
Install it yourself.
Create an account, confirm your e-mail with the code we send, take the free Community key from the Licenses page, and install with Helm.
Create an account