CSB-05
Source Code Auditing
We read application source line by line for vulnerabilities that dynamic testing and scanners miss.
Exhibit · Sample finding · CSB-05Report view
Debug flag bypasses role check
How a finding reads in our report: what we found, how we reached it, and how to fix it. The evidence that proves it sits underneath, line by line.
Evidence: working papers beneathIllustrative, not client data
1.1 — What we test
- 1.1.1
Line-by-line review
- 1.1.2
Bugs scanners miss
- 1.1.3
Static analysis
1.2 — Deliverables
- 1.2.1
Detailed vulnerability report
- 1.2.2
Executive summary
- 1.2.3
Remediation strategy
1.3 — Methodology
Five steps, from scope to report.
Every step is documented, so the report shows exactly how each finding was reached.
01
02
03
04
05
03 · In progress
01Queued
Project Kickoff
We start by writing down what is in scope.
- Security requirements
- Scope and boundaries
- Team
- Timeline
02Queued
Scoping & Planning
We plan the test before it starts.
- Review the environment
- Choose the test method
- Set risk ratings
- Prepare tools
03Queued
Security Assessment
We test by hand. Scanners are used where they help.
- Scanning, where it helps
- Manual testing
- Checks of the controls in scope
04Queued
Progress Tracking
You hear from us while the test is running.
- Weekly progress reports
- Findings written as they are confirmed
- Updated risk ratings
- Remediation recommendations
05Queued
Final Delivery
The written report, and a handover.
- Detailed vulnerability report
- Executive summary
- Remediation strategy
- Recommendations for future security work
1.5 — Next step
Who should we prepare your report for?
Type your company name to see it on the report cover and the scoping worksheet underneath. Hover over the cover to lift it.Tap the cover to lift it.
CyberSibSample
Security Assessment Report
Prepared for
Your company
ScopeDefined at kickoffFindings—Date2026