SOC 2

Make AWS logical access easier to explain and evidence.

Securitain turns your AWS IAM posture into clear, repeatable evidence for the logical-access themes auditors ask about — so SOC 2 prep is less of a scramble.

Technical evidence support, not certification. Securitain does not make any organization “SOC 2 certified.” It assesses AWS logical-access controls and maps findings to control areas to support your SOC 2 examination, which is performed by an independent CPA firm.

Why it matters

The problem teams bring to SOC 2

SOC 2 readiness depends heavily on logical access: who has privileged access, how they authenticate, whether access is least-privilege, and how exceptions are handled. Pulling that together from the AWS console by hand is slow and error-prone. Securitain produces consistent, evidence-backed findings across your accounts so you can explain and demonstrate your logical-access controls.

What Securitain evaluates today

AWS access controls, assessed read-only

Logical and privileged access across IAM
Authentication controls (MFA, console access, root)
Least-privilege and over-permissive identities
External-party access via cross-account trust
Monitoring-relevant access configuration
Exception handling via finding suppression with reasons
Remediation evidence and finding lifecycle
Example findings

From observation to evidence

Privileged role without least-privilege scopingRole ARN, effective permissions, wildcard actions, scan timestamp
User with console access and no MFAUser ARN, MFA status, login profile presence
Cross-account trust to a vendorTrust statement, external account ID, ExternalId condition
Accepted risk recorded as exceptionFinding ID, suppression reason, who recorded it
In the Compliance Center

How SOC 2 results appear

Each finding maps to the relevant SOC 2 control areas, with a justification drawer showing the check used, expected vs observed configuration, the affected account and ARN, an evidence timestamp, and remediation guidance. Securitain describes control areas rather than asserting authoritative control IDs.

1Finding generated with evidence
2Mapped to SOC 2 control areas
3Justification drawer with observed config
4Remediation guidance attached
5Included in the assessment report
Shared responsibility

What stays manual and organizational

Securitain supports

  • Repeatable evidence of logical and privileged access controls
  • Authentication and least-privilege findings with remediation
  • External-party access visibility for vendor reviews
  • Mapping of IAM findings to logical-access control areas

Your program completes

  • Control design and selection of Trust Services Criteria
  • Management assertions and system description
  • HR onboarding and offboarding processes
  • Change management and incident records
  • The CPA examination itself
Next phase

Planned — not current coverage

Broader monitoring and event-driven coverage
Automated evidence packages beyond IAM scope
Signed attestation drafts aligned to specific criteria
SOC 2 FAQ

Common questions

Does Securitain make us SOC 2 certified?

No. A SOC 2 report is issued by a licensed CPA firm after an examination. Securitain provides technical evidence for AWS logical-access controls that supports that examination — it does not certify or attest.

Which Trust Services Criteria does it help with?

Most directly the logical-access aspects of the Security/Common Criteria. Control design, governance, and the examination remain your and your auditor’s responsibility.

How does exception handling work?

Findings you formally accept can be suppressed with a recorded reason, so reporting reflects approved exceptions accurately.

Strengthen your SOC 2 access controls

Connect a read-only role and see how your AWS IAM findings support your SOC 2 evidence — with mapping, justification, and remediation guidance on every scan.