SOC 2 · For security and compliance teams at service organisations
Your controls run all year. With EA, so does the evidence.
Your runbooks, policies and evidence folders are enough for EA to run your SOC 2 programme. It checks your readiness, drafts the control and system descriptions, and gathers each control’s evidence from its owner across the period. Your Information Security Manager approves each piece, and your auditor tests it.
Try EA free. No card needed.
Organisations that run work on EA
The auditor reads the whole period, not the last week.
Evidence on a calendar
Access reviews each quarter, vulnerability scans each month, a restore test each quarter. A Type 2 report checks that each one happened when your policy says it would.
Held by people with releases to ship
The controls run inside engineering, IT and people operations. Each export and screenshot the period needs comes from someone whose own work is due.
The period closes on a date
Fieldwork follows soon after, and what wasn’t filed in month three is harder to find in month thirteen.
With EA running the period, the evidence is filed as each month passes, and fieldwork starts from a folder that’s already full.
What EA does
Control by control, month by month.
One Type 2 period, from scoping to the auditor’s sample requests. EA drafts, asks and keeps each reply with its control; your team runs the controls and decides.
01 / 05
- EA
Reads your controls, policies and any earlier report against the Trust Services Criteria you’ve chosen, and marks each criterion covered, partly covered or without a control. Gap Analysis
Your teamThe Information Security Manager sets the scope: which criteria, which systems, and whether this is a Type 1 or a Type 2.
- EA
Drafts the system description to the SOC 2 Description Criteria and each control description against the Trust Services Criteria in scope, the terms your auditor will test, from your runbooks, architecture notes and ticket history. Approvals
Your teamControl owners correct the detail, and the Information Security Manager approves both.
- EA
Sends each owner’s request when a control’s evidence falls due, quarterly for restore tests and monthly for scans, follows up, and keeps each reply with its control and month. Automations
Your teamThe Security Compliance Manager sets each control’s schedule once; owners reply with an export, a screenshot or a ticket link, and the Security Compliance Manager sees what is still due.
- EA
Flags a quarter with no restore test, or a hosting provider’s report that no longer covers your period, and asks the IT Manager or the Vendor Manager for what’s needed. EA Agent
Your teamThe owner supplies the record, or the Information Security Manager decides how to raise it with the auditor.
- EA
Drafts management’s assertion from the approved system description, matches each of the auditor’s sample requests to the evidence on file, and writes the reference into the auditor’s own spreadsheet. Autofill
Your teamThe Information Security Manager approves each evidence set and shares it by a link you can revoke; management signs the assertion; the auditor tests the controls and issues the report.
See EA take one of your controls from its first evidence request to your Information Security Manager’s approval.
Book a demoThe next period picks up where this one closed.
No restart
The approved descriptions carry over, and each control’s requests keep coming round on its own schedule. The American Institute of Certified Public Accountants proposed revised criteria in October 2026; once they are final, EA reads your descriptions against them and marks what each owner should revisit.
Between reports
When customers ask what has changed since the period ended, EA drafts management’s bridge letter from the changes on file, for management to sign.
Exceptions, followed up
If the auditor noted an exception, the evidence of its fix becomes one of the first requests of the new period.
Your customers’ questionnaires
When a customer sends its own security questionnaire, EA drafts the answers by reference to your report and the evidence you’ve already approved. Read how EA answers vendor security assessments
- Control
- Backups and restore
- Evidence
- Restore test, third quarter
- Filed by
- IT Manager
- Approved by
- Information Security Manager
- Approved on
- 14 October
EA’s own security
Built for evidence you’d rather not email.
A SOC 2 programme puts production screenshots, the system description and the auditor’s exceptions in one place. You decide who opens it. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.
- Hosted your way
EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.
- Access
Single sign-on, which you can enforce, and an access list for each workspace.
- Support access
EA staff see your data only in a time-limited window you open.
- Testing
An independent firm runs a penetration test on EA every year.
- Security contact
EA’s security team is at security@eaglobal.ai.
In the demo, lock a programme workspace to the people your Information Security Manager names, before any evidence goes in.
Book a demoChoosing how to run the period.
| Compared with | What it does well | What EA adds |
|---|---|---|
| A spreadsheet and a shared drive | Familiar, cheap, and auditors accept it. | Each control’s evidence is filed by month as it arrives, with its owner, so a missing quarter shows months before fieldwork. |
| Alongside compliance automation software | Collects technical evidence from your systems, such as cloud configuration and code repository settings, on its own. | Drafts the policies and the control and system descriptions around that evidence from your own documents, asks each owner for what only they hold and follows up, and brings each piece to your Information Security Manager to approve. |
| AI that helps one person draft | Writes a policy or a control description quickly. | Runs the whole period: each control’s evidence requested, filed and approved, not one document at a time. |
FAQ
What SOC 2 owners want to know.
Control by control, on each one’s own schedule. In October, EA asks the IT Manager for the third-quarter restore test and the Head of Engineering for the month’s vulnerability scan, follows up with the People Operations Lead on new starter checks, and keeps each reply with its control and month, so fieldwork starts from evidence already on file.
Your auditor, a licensed certified public accountant (CPA) firm. It examines your controls against the Trust Services Criteria and writes the opinion; EA prepares what it examines.
EA writes each description from the runbooks, tickets and policies you hand it, with the source beside each section. If your change policy promises peer review and nothing on file shows one for a team, EA marks that control “Needs evidence” and asks its owner, and nothing reaches the auditor until your Information Security Manager approves it.
The people you add to the programme’s workspace. When fieldwork starts, you share the approved evidence with your auditor by a link with an expiry date, and you can close it early.
They advise on scope and control design. EA turns that advice into descriptions, evidence requests and a full folder, the work that would otherwise land on your team.
Yes: last year’s report, your control list and the evidence folders as they stand. Our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.
The descriptions are the same. A Type 1 needs evidence that each control is in place on one date; a Type 2 needs it across the period, so EA requests it on each control’s own schedule rather than once.
Your next SOC 2 period, without the fieldwork scramble.
One quarter’s evidence, to your Information Security Manager.
Where SOC 2 sits among your other work.
Related solutions
- ISO 27001Many of the controls overlap, so one owner’s evidence can serve both audits.Security and IT
- HIPAAWhere you handle US health data, the same access and logging controls answer a second set of safeguards.Security and IT
- CAIQ and SIGStandard questionnaires that customers often accept answers to by reference to your report.Security and IT
By industry
SoftwareThe controls run in the deploy pipeline and the cloud console, so EA’s requests go to the engineers who run them.
Healthcare and life sciencesDigital health suppliers selling to US buyers are asked for a SOC 2 report alongside their European obligations.
Public sector and defenceSelection questionnaires, declarations and the carbon reduction plan, signed off by the right director.
Banking and building societiesThe operational resilience self-assessment and supplier reviews, attested by name.
Asset and investment managementInvestors’ DDQs, operational due diligence and the Principles for Responsible Investment report.
InsuranceBroker questionnaires, Lloyd’s confirmations and the own risk and solvency assessment.
Construction and infrastructureScheme renewals, prequalification and ISO evidence, including international engineering, procurement and construction projects.
Manufacturing and consumer goodsCustomers’ supplier questionnaires, Sedex and the conflict minerals template.
Energy and utilitiesThe CSRD statement, CDP, regulator returns and the network and information security self-assessment.
Legal firmsPanel questionnaires, the professional indemnity renewal and Lexcel evidence, signed off by a partner.
Accounting firmsClients’ security questionnaires and the firm’s anti-money laundering return.
ConsultingClients’ vendor due diligence, framework tenders and the certificates behind them.

