Alfe Corona

Professional summary

Cybersecurity practitioner demonstrating hands-on architecture and engineering through Exposure Control, a working portfolio reference implementation that connects security findings to explainable priority, recorded ownership, tracked remediation work, and evidence-gated closure. Focused on secure automation, auditability, and clear communication between security, engineering, and risk stakeholders.

Selected cybersecurity project

Exposure Control — Cyber-Exposure Management Reference Implementation

Live portfolio · Completed synthetic demo · Source code

• Designed and implemented a portfolio vertical slice that normalizes security findings, applies deterministic P0–P4 scoring, and creates or updates GitHub Issues that record an owner identifier, stable identity, priority, and evidence.
• Built JSON/JSONL file ingestion, a GitHub Issues workflow adapter, SQLite and PostgreSQL persistence, forced tenant row-level-security policies, schemas, dashboard generation, and idempotent workflow identities.
• Implemented a closure gate that checks tenant and exposure identity, logical source separation, evidence freshness, and a resolved outcome; the demo separates the logic inside one GitHub Actions environment.
• Added scheduled and on-demand dependency and repository scans, CI on pull requests and main updates, SHA-pinned Actions, restricted workflow-token permissions, a non-root container, and Kubernetes deployment references.

Demonstrated capabilities

Security architecture; threat modeling; vulnerability management; risk prioritization; remediation orchestration; Python; PostgreSQL; SQLite; JSON Schema; GitHub Actions; GitHub Issues; containers; Kubernetes references; CI/CD; secure software supply chain controls; observability; technical documentation.

Project evidence

• Successful CI evidence for historical public main commit 4db8b02, verified August 19, 2026.
• Four scheduled and on-demand scanner categories: dependency, source, configuration, and secret findings.
• Public, successful synthetic lifecycle run with a linked GitHub Actions workflow record.
• Public code, architecture decisions, threat model, deployment guidance, and production limitations.

The repository enforces a coverage gate. A single coverage percentage is intentionally omitted until statement and branch metrics are labeled consistently. These are repository checks, not customer outcomes.