WEBVTT

1
00:00:00.000 --> 00:00:04.000
Skylos Cloud · Chapter 22: SOC 2 evidence report
Turn your scans, fixes and pull requests into evidence an auditor can test.

2
00:00:04.000 --> 00:00:11.000
Step 1: From scans to an auditor's evidence
Trusted CI scans and your pull requests become a SOC 2 pre-assessment. You add what only you can write, and the auditor samples from the files.

3
00:00:11.000 --> 00:00:18.500
Step 2: Check which projects count
Compliance reports, then Step 1. Only trusted CI scans of the default branch count. An upload from a laptop doesn't.

4
00:00:18.500 --> 00:00:25.500
Step 3: Pick SOC 2
Each framework has its own report. It's charged once, and every format downloads free.

5
00:00:25.500 --> 00:00:32.500
Step 4: Choose projects and the audit period
Pick the repositories in scope and the dates your auditor will test, up to 12 months.

6
00:00:32.500 --> 00:00:40.000
Step 5: Signed and ready
Skylos signs the report and stores it. The CSV files are the populations an auditor samples from.

7
00:00:40.000 --> 00:00:47.000
Step 6: Start with the result
Policy met, fixes due: one critical dependency advisory, still inside its fix-by date. It's Skylos's policy result, not a SOC 2 opinion.

8
00:00:47.000 --> 00:00:54.000
Step 7: Management's assertion
Every SOC 2 report opens with one, signed by an officer. Skylos never writes it for you; it gives you a draft to adapt.

9
00:00:54.000 --> 00:01:02.000
Step 8: Controls, tested like an auditor would
Each control has a test, a population and a result in SOC 2 wording: no deviations, or x of y.

10
00:01:02.000 --> 00:01:09.000
Step 9: It says what it couldn't test
GitHub didn't report reviews for this merge, so the approval test says not evidenced instead of passing.

11
00:01:09.000 --> 00:01:16.500
Step 10: Readiness, criterion by criterion
A criterion is Implemented only when every Skylos test for it passed. One unproven test makes it Partially implemented.

12
00:01:16.500 --> 00:01:23.500
Step 11: Deviations, with your response
Each deviation is listed with a place for management's response. Write it in SOC 2 answers and it prints here next time.

13
00:01:23.500 --> 00:01:30.500
Step 12: Send auditors the external summary
The same tests and results, without code locations, issue text or people's emails.

14
00:01:30.500 --> 00:01:37.500
Step 13: Auditors can check it's genuine
The verification page confirms the copy is unchanged and signed by Skylos, without showing any of its content.

15
00:01:37.500 --> 00:01:45.000
Step 14: Fill in what only you can write
SOC 2 answers: the system description, approved control wording, readiness owners and deviation responses. Save them and regenerate.

16
00:01:45.000 --> 00:01:52.000
Recap: Only trusted CI scans count · Pick projects and an audit period; charged once · Controls tested as x of y, in SOC 2 wording · It says what it couldn't test · Send the external summary; auditors can verify it
Next: Chapter 23 · AI review
