Evidence Preparation Guide

We know that an upcoming audit can be daunting, so we’ve pulled together a short guide to explain how to prepare your evidence for your upcoming SOC 2 audit.

Have a read, and if you have any other questions drop us a line!

hello@tempoaudits.com

What is the Purpose of this Guide?

The table below provides a comprehensive list of controls that form the foundation of our SOC 2 audit framework, addressing the Trust Service Criteria for Security, Availability, and Confidentiality.

Accompanying this list is a guide detailing the types of audit evidence applicable to meeting each control requirement. Multiple examples are provided for each control, as compliance can often be demonstrated through different forms of evidence. Each example serves as an option rather than a complete list of requirements, offering flexibility in how the controls can be satisfied.

SOC 2 Security, Availability and Confidentiality Control Framework - Example

We hope this short guide helps you when preparing your evidence for your SOC 2 audit, but if you have any more questions - just shout!

Control Name

New hire access approval


Terminated employee access removal


Periodic user access reviews



Role-based access control




Multi-factor authentication


User listings showing unique IDs




Customer agreements





Change management policy




Segregated change environments




System-enforced code reviews




System-enforced release approval




Testing of changes






Code of conduct





Data handling policies





Register of confidential data




Retention period of data



System boundaries for data protection




Vulnerability scans





Penetration testing






Resolution of vulnerabilities






Firewalls at access points




Antivirus installed on devices




Systematically enforced endpoint device restrictions



Encryption of data-at-rest




Encryption of data-in-transit




Network monitoring alerts




New hire background checks





Incident management policies




Incident tickets or records





Incident response plans




Emergency Response Team




Annual review of incident response plans



Post-incident reviews







Board of Directors meetings



Responsibilities of Board of Directors




Board oversight of information security





Control framework responsibilities




Annual review of policies




Log of control failures





Conduct Control Self-Assessments





Acceptable use policy




Information security policies



Vulnerability management policy





Asset Management Policy





Access control policy




Password policy




Cryptography policy





Maintains Asset Inventory



Operating system updates



Data disposal requirements





Employee performance reviews





Employee security awareness training





Risk Management Policy




Risk assessments





Risk assessment of fraud





Risk assessment of operating changes




Risk management strategies





System redundancy






Backup configuration and schedule



Backup restoration tests




Business continuity plans





Disaster Recovery Plan




Cyber liability insurance




Backup policy





Load balancer






Annual BCP testing






Organisation chart






Employee job descriptions





Documented policies with responsibilities




Responsibilities for information security and privacy




New hire employment contracts



System monitoring tools




Auto-scaling configuration




Version control software




Annual vendor risk assessment




Vendor management policy





Vendor agreements

Description

New user access privileges to critical systems are approved by management prior to provisioning.

A defined terminations process is followed including revocation of user access from systems in a timely manner.

User access reviews are performed at least quarterly to confirm user access to in-scope systems is appropriate.

An assessment of functional roles and system access privileges has been completed to identify the requirements for the segregation of duties.

Multi-factor authentication or equivalent is applied across in-scope systems.

User access accounts to the network, infrastructure, and systems holding customer data are assigned to individual users.


Customer commitments, requirements, and responsibilities are outlined and communicated through formal service terms.



Documented change control policies and procedures are in place to guide personnel in the change management process.


Development and test environments are logically separated from the production environment.



Code developments require a system-enforced peer review prior to merging with the master code branch.


Change releases require a system-enforced review and approval prior to deployment.



System changes are tested based on the type of change prior to implementation.




The code of conduct is documented to communicate conduct standards and enforcement procedures.



The requirements for managing data are established in the data classification, handling, retention and disposal policies.



A register of the types and sources of confidential data collected and processed is maintained to track assets and storage locations of confidential data.

The retention period of confidential data is classified based on the purpose and type of data and location the data is stored.

Confidential data is maintained within the system boundaries at all times where security controls are applied to restrict access to authorised individuals.

Vulnerability scans are performed at least quarterly.




Independent penetration testing is conducted annually.





Vulnerabilities identified from the penetration tests, vulnerability scans, and any other sources, are centrally logged, classified and followed through to resolution in a timely manner based on their severity.

Firewalls are used at external points of connectivity to the infrastructure and network.



Anti-virus software is installed to protect company devices.




Systematically applied security restrictions are used to protect against malicious software and data leakage.


Data at rest in the production database(s) is automatically encrypted.



Data in transit to the infrastructure is automatically encrypted.




Automated alerts and log reviews are used to identify and respond to suspicious network activity.



Background checks are completed for candidates prior to employment.





The incident management policies and procedures document the approach to identifying, reporting, evaluating, classifying and handling incidents.

Incident management processes are defined and followed for identification, assessment, classification, response, communications to interested parties, and resolution.

Incident response plans are defined to provide guidelines for responding to major incidents including security breaches.


The established emergency response team is defined to respond to major adverse events in a timely manner.


The incident response plans are reviewed and updated at least annually to ensure they remain current and effective.


Root cause analysis is conducted on high-severity incidents to determine lessons learned and updates required to the incident response plans, as well as raise change requests for permanent fixes to prevent recurrence.

Board of Directors meetings are held at least annually for organisational oversight and governance.

The Board Charter sets out the responsibilities and scope of the Board of Directors.



The Board is responsible for oversight of the systems and data security with review at least annually.



Management are assigned ownership of ongoing monitoring of the effectiveness of controls and that key policy and process requirements are being adhered to.

Key policies and processes are reviewed and updated at least annually to confirm their effectiveness, accuracy and compliance.

Management tracks whether control failures, breaches of policies and procedures, customer complaints and other issues are assessed, tracked and monitored through to resolution, as applicable.

The control framework is reviewed at least annually by the control owners to ensure the control descriptions and owners are accurate, and that the controls are operating effectively as described.

The acceptable use policy sets out the roles, responsibilities and requirements to maintain the security of systems, data and endpoint devices.

The security policies set out the requirements for managing information security across the organisation's operations.

A vulnerability management program is defined and documented to assess and manage the technical security of systems including identification, prioritisation and resolution of vulnerabilities.

The asset management policy establishes the roles, responsibilities and requirements for managing critical information assets to protect their security, availability, and integrity.

The access control policy sets out the required system access controls for secure authentication and account use.

The password policy sets out the requirements and guidelines for using secure and strong passwords.


The Cryptography Policy defines the required use of encryption and managing encryption keys to secure systems and data.


An inventory of system assets and components is maintained to classify and manage the information assets.

A formal process is defined and followed to ensure operating system versions for devices are updated regularly.

The defined data disposal guidelines and requirements set out the process for ensuring data is erased prior to disposal of system assets.


Employee performance reviews are conducted at least annually.





Security awareness training is provided to employees.





Documented policies and procedures are in place to guide personnel when performing a risk assessment.


Risk assessments are completed at least annually to identify and analyze the risks and identify any required mitigation actions.


The risk assessment process considers the potential for fraud including malicious acts of employees or other users of the system.


The risk assessment process identifies and assesses changes that could significantly impact the system of internal control.


Management develops risk mitigation strategies to address risks identified during the risk assessment process.



The system is designed with multiple availability zones and redundancy to support continued availability in the event of a failure.



Backups of the application and database are performed daily.




Backup and restoration tests are performed on at least an annual basis to ensure the recovery controls are effective.


The business continuity plans document the scenarios, impacts, key stakeholders, response plans, escalation points and communication channels to effectively manage critical events.

The Disaster Recovery Plan includes defined procedures to recover from significant events, and is reviewed and updated at least annually.

The organisation has purchased insurance to offset or compensate for the financial loss of an adverse event with the services.


The backup policy establishes the requirements for backups and recoverability.



A load balancer is used to automatically distribute traffic across multiple availability zones.




The business continuity plan is tested at least annually to ensure the response plans to critical events are effective.



The organisation chart documents the reporting lines, accountable executives, team and individual roles, and is updated whenever there are changes in personnel.


Job descriptions are documented for employees and management setting out the responsibilities, role requirements, and any key accountabilities.


The documented policies and procedures establish roles, responsibilities, and area accountabilities.


The responsibilities for information security and privacy are established, documented and communicated to employees.



Employment contracts are formed with employees.




Monitoring tools are used to identify and evaluate system performance, capacity, availability, and security-related indicators.


Processing capacity is configured to auto-scale to meet processing demand.



Version control software is used to track changes to the source code and provide rollback capability if required.


An annual vendor risk assessment is completed to ensure the identification and treatment of risks remains accurate and appropriate.


Management has defined a third-party vendor risk management approach for evaluating third-party risks.



The entity's third-party agreements outline and communicate; the scope of services, roles and responsibilities, terms of the business relationship, communication protocols, compliance requirements, service levels and just cause for terminating the relationship.

Audit Evidence Examples

Approval form signed by authorised personnel and/or system logs showing access granted.

Documentation of termination notice, system logs showing access revoked, and confirmation emails.


Review reports, sign-off by reviewer, and evidence of action taken on anomalies (if required).


Screen captures of system settings and documentation of approval process by stakeholders.



List of privileged users, comparison to approval records, and evidence of removed or modified access.

User access request forms, system logs showing the assignment of access to individual users, and evidence of periodic reviews of user access privileges.

Copies of signed service agreements, records of customer onboarding sessions, and documentation of service terms communicated via email or other formal channels.

Copies of the change management policy, change request forms with approvals, and logs of changes tracked through a change management system.

Network architecture diagrams, access control lists for development, test, and production environments, and system configuration logs showing enforced separation.

Code review logs, pull request histories from a version control system (e.g., Git), and documentation of peer review sign-offs.

Change request forms with documented approvals, deployment logs showing approval timestamps, and system logs enforcing the change management workflow.

Test plans and results, approval of testing outcomes, and records showing different levels of testing (e.g., unit, integration, user acceptance) based on the nature of the change.

Copies of the code of conduct, training attendance records, acknowledgment forms signed by employees, and disciplinary action logs for violations.

Data classification policy documents, records of employee training on data handling policies, and logs or reports showing adherence to retention and disposal schedules.

Confidential data register, data flow diagrams indicating data sources and storage locations, and audit logs tracking data collection and storage.


Data retention policy, retention schedule for various data types, and system configurations enforcing retention periods.

System access logs showing restricted access to confidential data, security policy documents, and role-based access control (RBAC) configuration files.

Quarterly vulnerability scan reports, records of scan scheduling and execution, and logs showing remediation of identified vulnerabilities.

Penetration test reports, engagement contracts with third-party security firms, and documentation of remediation actions based on penetration test findings.

Vulnerability management logs, classification of vulnerabilities based on risk, and records of vulnerability resolution with time stamps.



Network architecture diagrams showing firewall placements, firewall configuration logs, and reports of firewall rule changes and updates.

Anti-virus software installation logs, update logs showing that the software is current, and reports of any detected malware or security threats.

Security policies defining restrictions, system configurations enforcing security policies, and logs of security events related to malware or data leakage.

Database encryption policy, encryption configuration settings, and audit logs showing the encryption status of production databases.

Network configuration settings showing encryption protocols (e.g., TLS, VPN), encryption certificates, and logs confirming data in transit is encrypted.

Logs of automated alerts, incident response reports triggered by suspicious activities, and configuration settings of the alerting system (e.g., SIEM logs).

HR records showing background check results, confirmation of background checks completed before the employment start date, and vendor agreements for background check services.

Incident management policies, incident classification matrix, and documented procedures for incident reporting and escalation.


Incident response logs, post-incident reports, communication logs with stakeholders, and a classification report of incidents.



Incident response plan documentation, examples of past incident response actions, and approvals of the incident response plan.

Emergency response team rosters, communication logs from emergency response situations, and training records of emergency response personnel.

Documented annual review records of the incident response plan, change logs of updates made to the plans, and approval records of the updated plans.

Root cause analysis reports, action items and lessons learned documents, and change requests raised as a result of root cause analysis.



Board meeting minutes, agendas showing discussion points related to governance, and attendance records of Board members.

Copy of the Board Charter, records of Board members signing acknowledgment of their responsibilities, and Board meeting materials referencing the Charter.

Board meeting minutes showing discussions and decisions regarding system and data security, risk assessment reports presented to the Board, and annual review records of security policies.

Management responsibility matrices, monitoring logs showing ongoing review of controls, and periodic compliance reports submitted by management.

Policy review schedules, updated policy documents, sign-offs from policy owners, and records of changes made during the annual review process.

Incident tracking logs, root cause analysis reports, records of corrective actions, and audit trails showing the resolution of policy breaches and complaints.


Control framework documentation, annual control review reports, control owner sign-offs, and records of testing control effectiveness.



Acceptable use policy documents, employee acknowledgment records of the policy, and monitoring reports on policy adherence.


Security policy documents, risk assessments related to information security, and logs showing enforcement of security measures.

Vulnerability scan reports, vulnerability management policies, logs of vulnerability remediation, and prioritisation matrices for handling vulnerabilities.


Asset management policy, inventory of information assets, asset classification logs, and records of asset audits.



Access control policy documents, system access logs, records of periodic access reviews, and user access request forms.

Password policy documents, system configurations enforcing password complexity, and logs of password resets or updates.

Cryptography policy documents, encryption key management logs, system settings showing encryption enabled, and audit logs showing the use of encryption.

Inventory records of system assets, asset classification and tagging reports, and logs of inventory audits or updates.

Patch management policy, update logs showing OS versions and patch levels, and change management records documenting OS updates.

Data disposal policy documents, certificates of data destruction, system logs showing data wipe activity, and third-party service provider contracts for secure disposal.

Performance review forms, employee acknowledgment of the review, schedules of annual performance reviews, and signed documentation of review discussions.

Training materials, attendance records or certificates of completion for security awareness programs, and follow-up assessments or quizzes demonstrating understanding.

Risk assessment policy and procedure documents, records of completed risk assessments, and documented review of risk assessment outcomes.

Annual risk assessment reports, risk registers, meeting minutes discussing identified risks, and documentation of mitigation strategies implemented.

Fraud risk assessment documents, internal audit reports on fraud prevention controls, fraud incident reports, fraud risk considered as part of the organisation or department risk assessment.

Risk assessment documents, change management logs, risk impact analysis reports, and documentation of control testing after significant changes.

Risk mitigation plans, action items from risk assessment meetings, records of implemented controls or countermeasures, and progress tracking reports on mitigation efforts.

System architecture diagrams showing redundancy and availability zones, system failover tests, uptime monitoring reports, and service level agreements (SLAs) with cloud providers.

Backup logs showing successful daily backups, reports from backup software, and restoration tests confirming data recovery from backups.

Backup test logs, restoration test reports, and documentation showing recovery times and effectiveness of the restoration process.

Business continuity plan documents, scenario testing reports, records of stakeholder engagement meetings, and communication logs during BCP tests.


Disaster recovery plan documents, annual review logs, test results from disaster recovery drills, and updated versions of the DR plan showing changes.

Insurance policy documents, coverage summaries, and communication with insurance providers confirming coverage for adverse events.

Backup policy documents, logs showing adherence to backup frequency requirements, and audit trails of data restoration testing in compliance with the policy.

Load balancer configuration settings, system architecture diagrams showing the use of load balancers, traffic distribution logs, and uptime monitoring reports confirming balanced traffic.

Test results of business continuity plan drills, meeting minutes discussing test outcomes, improvement plans based on test findings, and documentation of the annual review.

Updated organisation chart, records of changes made to roles and reporting lines, approval records of the updated chart, and employee onboarding or offboarding records.


Job description documents, acknowledgment forms signed by employees, role definition approvals by HR or management, and performance review records linked to role requirements.

Policy and procedure documents, role and responsibility matrices, acknowledgment forms from employees, and documentation of policy training sessions.

Information security and privacy policy documents, employee training records, signed acknowledgment forms, and security-related communications (e.g., email updates, posters).

Signed employment contracts, offer letters, records of employee onboarding, and legal reviews of employment contracts for compliance.

Monitoring tool configuration settings, performance logs, capacity usage reports, security alert logs, and incident response records based on monitoring data.

System configuration showing auto-scaling settings, logs of processing capacity adjustments during peak demand, and reports on the effectiveness of auto-scaling.

Version control logs (e.g., Git), change request forms, rollback event logs, and code review documentation within the version control system.

Vendor risk assessment reports, vendor risk rating logs, meeting minutes discussing vendor risks, and action plans or mitigation strategies for high-risk vendors.

Third-party vendor risk management policy, vendor risk assessment criteria, vendor contracts reviewed for compliance, and audit reports on third-party risk evaluations.

Signed third-party agreements, service level agreements (SLAs), compliance requirement clauses within contracts, and records of vendor performance reviews.


Mapping to the SOC 2 Criteria


CC6.2, CC6.3



CC6.2, CC6.3, CC6.5, C1.2




CC6.3, CC6.5




CC6.1, CC6.3, C1.1





CC6.1, CC6.6



CC6.1, CC6.2, CC6.3





CC2.3






CC8.1





CC8.1





CC8.1





CC8.1





CC8.1






CC1.1, CC1.4, CC1.5





C1.1






C1.1





C1.2




C1.1





CC4.1, CC4.2, CC5.2, CC6.6, CC6.8, CC7.1




CC4.1, CC4.2, CC5.2, CC6.6, CC6.8, CC7.1





CC7.2, CC7.3, CC7.5, CC7.1







CC6.6





CC6.8





CC6.6, CC6.7, CC6.8





CC6.1, CC6.7





CC6.6, CC6.7





CC6.8, CC7.1, CC7.2





CC1.1, CC1.4






CC2.2, CC5.2, CC5.3





CC2.3, CC7.3, CC7.4, CC9.1, CC4.1






CC2.2, CC2.3, CC7.3, CC7.4, CC7.5, CC9.1




CC7.3, CC7.4





CC7.5





CC2.2, CC2.3, CC4.2, CC7.3, CC7.4







CC1.2




CC1.2





CC1.2, CC4.2






CC4.1,CC4.2





CC3.1, CC6.1, CC5.3





CC4.2






CC2.1, CC4.1, CC5.1






CC1.1, CC1.5, CC2.2, CC6.6, CC6.7, CC6.8, C1.1, C1.2




CC1.1, CC2.2, CC3.1, CC5.2, CC5.3, CC6.1



CC2.3






CC2.1, CC6.1, CC6.5






CC6.2, CC6.3




CC6.1




CC2.1, CC5.2, CC6.8





CC2.1, CC6.1, CC6.5




CC6.8




CC6.5, C1.2






CC1.4, CC1.5






CC1.4, CC2.2, CC5.2, CC6.6, CC6.8






CC3.1, CC3.2, CC3.3, CC3.4





CC3.2, CC3.3, CC3.4, CC5.1, CC5.2





CC3.3






CC3.4





CC3.2, CC3.3, CC5.1






CC9.1, A1.1, A1.2






CC7.5, CC9.1, A1.2, A1.3





CC4.1, CC5.2, CC5.3, CC9.1, A1.3





CC7.5, CC9.1






CC7.5, CC9.1, A1.2





CC9.1





CC9.1, A1.2





A1.1






CC5.2, CC9.1, A1.2, A1.3






CC1.3, CC1.5, CC3.4






CC1.3






CC1.3, CC2.2, CC3.1, CC5.3, CC5.2, CC1.4




CC1.3, CC1.5






C1.1





CC7.2, A1.2





A1.1





CC7.1, CC8.1





CC3.2, CC4.1, CC9.2





CC2.3, CC3.2, CC3.4, CC9.2






CC2.3, CC3.2, CC9.2