← ventsislava.com Compliance Evidence Collector
SOC 2
PORTFOLIO PROJECT
SYSTEM STATUS: ACTIVE

Compliance Evidence
Collector

Automated SOC 2 evidence collection from Identity, GitHub, and AWS sources. Evaluates findings against YAML-defined controls and generates audit-ready reports.

Architecture

How it works

Click any component to see implementation details.

🔌
API Sources
Okta · GitHub · AWS
Source Connectors
Each source has a dedicated connector module with collect_evidence(). Uses bearer token auth, handles pagination, and normalizes output into a standard evidence dict.
→
📋
YAML Controls
soc2_controls.yaml
Compliance-as-Code
Controls are defined in YAML — no code changes needed to add new checks. Each control specifies: check_field, operator, threshold, and severity.
→
⚙️
Evaluator
PASS · WARN · FAIL
Evaluation Engine
Compares evidence values against thresholds using safe operator lookup (no eval()). Three-tier result: PASS → WARNING → FAIL with human-readable messages.
→
📊
Reports
JSON · CSV
Audit-Ready Output
Structured reports with control ID, status, severity, actual values, and thresholds. Exportable as JSON for automation or CSV for spreadsheet review.
Evidence Collection

Select a scenario and collect evidence

SCENARIO:
🔐
Identity Provider
Simulated Okta-style identity data: MFA enrollment, inactive accounts, admin access reviews.
CC6.1CC6.2 CC6.3CC6.6
🐙
GitHub
Repository security: branch protection, PR review requirements, secret scanning coverage.
CC8.1CC8.1.2 CC8.1.3
☁️
AWS
Cloud infrastructure: CloudTrail logging, encryption at rest, root account MFA enforcement.
CC7.1CC7.2 CC7.3
compliance-evidence-collector
Evaluation Results
Control Name Status Severity Details
Control Definitions

Compliance-as-Code

Controls are defined in YAML — add new checks without touching code.

Under the Hood

Code Walkthrough