I build small, reproducible security tools that favor authorization, read-only defaults, synthetic fixtures, and deterministic tests. This profile documents hands-on work across Windows security diagnostics, secure software development, detection engineering, and incident response.
| Project | What it demonstrates | Status |
|---|---|---|
| Windows Driver Policy Auditor | Read-only Windows Code Integrity diagnostics, offline XML analysis, structured findings, and HTML reporting | |
| SecurePatch Lab | Regression-tested fixes for common application-security defects plus deterministic SBOM generation | |
| Detection Engineering Lab | Sigma and YARA artifacts, ATT&CK mapping, synthetic positive/negative telemetry, and rule regression tests | |
| Incident Response Evidence Collector | Read-only triage collection, redaction, normalized timelines, SHA-256 manifests, and offline verification |
- Work only on systems and data that are owned or explicitly authorized.
- Prefer offline, read-only, and deterministic workflows.
- Use synthetic fixtures instead of malware samples or third-party private data.
- Keep safety boundaries, expected behavior, and limitations visible in each repository.
- Require automated tests and reviewable output before publishing a release.
- Python packaging, unit tests, GitHub Actions, release notes, and changelogs
- Windows Code Integrity and driver-policy diagnostics
- Secure coding, patch validation, and software supply-chain metadata
- Sigma/YARA rule authoring and detection regression testing
- Incident-response evidence handling, redaction, timelines, and integrity manifests
Every featured repository includes architecture documentation, sample reports generated from local synthetic fixtures, automated CI, and tagged releases.