SOC 2 · Attestation standard of the AICPA
SOC 2 asks for controls that work.
Kodator supplies proof of them.
For a SOC 2 report you have to show the auditor that you detect and fix vulnerabilities and ship changes in a controlled way. Kodator records exactly this work. The product does not have a SOC 2 report of its own yet.
- Not a lawWhat it is
SOC 2 is an attestation standard of the AICPA. Customers and procurement ask for the report, not a legislator.
- Type 1 / Type 2Report types
Type 1 describes the controls at a point in time, Type 2 their effectiveness over a period.
- MappingState in Kodator
Kodator maps its evidence to the criteria. A built-in SOC 2 report does not exist yet.
Scope
Who SOC 2 matters to
SOC 2 is aimed at service organisations that process data of their customers. The audit follows the Trust Services Criteria: security is always included; availability, processing integrity, confidentiality and privacy are added depending on the scope.
SaaS and cloud providers
Above all when they sell to companies in the USA or to international groups.
IT and software service providers
Whoever operates or develops systems for customers and shows up in their vendor reviews.
Suppliers of regulated customers
Banks and insurers often ask their service providers for an audit report such as SOC 2.
SOC 2 does not end with a certificate but with the report of an independent auditor. Which evidence is accepted is the auditor's decision.
Step by step
The road to the SOC 2 report, and who contributes what
Most of SOC 2 is about organisation and processes. Kodator contributes where vulnerabilities, changes to software and their traceability are concerned.
How to read the steps
Kodator 1 / 10Kodator produces the evidence from scans and remediation.
Kodator helps 5 / 10Kodator supplies part of the evidence. The task stays with you.
You 4 / 10Outside of what a scanner can give evidence for.
Define scope and report type
Which system is audited, which categories besides security, Type 1 or Type 2?
- Kodator supplies
- No contribution.
- Stays with you
- A decision, agreed with your customers and the auditor.
Assess risks and define controls
You identify the risks to your objectives and decide which controls address them.
- Kodator supplies
- Findings with a risk score from CVSS, exploit probability and the flag for actively exploited vulnerabilities, and documented risk acceptances with justification and expiry date, as input.
- Stays with you
- The risk assessment of the organisation and the choice of controls.
Establish policies and organisation
Responsibilities, policies, training, and the handling of vendors and security incidents.
- Kodator supplies
- No contribution.
- Stays with you
- Write the policies, put them into practice and show that they are followed.
Protect access
Logical and physical access to systems and data is restricted, credentials are protected.
- Kodator supplies
- One aspect only: the scan finds credentials and keys that sit in source code and shows open hits.
- Stays with you
- Authorisation concept, authentication, access reviews and everything else under CC6.
Detect vulnerabilities continuously
You use procedures to detect new vulnerabilities and risky configuration changes.
- Kodator supplies
- Scheduled scans and scans on every change across source code, dependencies, containers, infrastructure as code and the running application; daily matching of stored SBOMs against new vulnerabilities; a complete run history.
- Stays with you
- Monitoring of systems and networks outside the software Kodator scans.
Fix vulnerabilities in time
Detected vulnerabilities are assessed and fixed according to your own rules.
- Kodator supplies
- Remediation deadlines per severity, overdue findings, times to fix and every decision in the audit log.
- Stays with you
- Set the deadlines in a policy and carry out the remediation.
Ship changes in a controlled way
Changes to software are authorised, tested and approved before they are shipped.
- Kodator supplies
- A security scan per pull request with a status in the Git hosting (GitHub, GitLab, Azure DevOps, Bitbucket Cloud), and a pipeline that stops on new findings at or above a chosen severity.
- Stays with you
- Approval process, four-eyes principle, functional tests and control of the deployment.
Collect evidence over the audit period
For a Type 2 report the controls must be shown to have operated over months.
- Kodator supplies
- Scan history, finding reports as PDF, SBOMs and a hash-chained audit log whose integrity can be verified.
- Stays with you
- Evidence for all other controls and the mapping to your control catalogue.
Close gaps before the audit
A readiness assessment shows which controls are missing or not evidenced.
- Kodator supplies
- No contribution.
- Stays with you
- The readiness assessment and closing the gaps.
Audit by an independent auditor
The auditor tests the controls and issues the SOC 2 report.
- Kodator supplies
- No contribution.
- Stays with you
- Engage the auditor, present the evidence and answer questions.
In the product
No SOC 2 report of its own yet
Unlike for PCI DSS and the CRA, Kodator today has no report that arranges the evidence by SOC 2 criteria. The evidence comes from the existing views and exports.
- CC7.1
- CC8.1
- CC6
- CC3
- Finding reports per tenant, project or scan as PDF
- Scan history and run history of the schedules
- SBOM per asset as CycloneDX JSON and PDF
- A hash-chained audit log that cannot be changed unnoticed
What Kodator is not
Kodator has no built-in SOC 2 report. Whether a piece of evidence is sufficient is your auditor's decision. Kodator replaces neither your controls nor the audit. As a vendor, Kodator itself currently has no SOC 2 report and no ISO 27001 certification.
Next step
See Kodator on your own code.
Tell us which product and which requirement you are dealing with. In a demo we show you which evidence Kodator supplies for it, and which it does not.