AMN Security — Cybersecurity Portfolio

Penetration Testing • Vulnerability Assessment • Security Reporting • Remediation Strategy

---

👋 Professional Summary

Security researcher and penetration testing practitioner focused on professional vulnerability analysis, technical risk communication, and practical remediation guidance.

This GitHub profile is organized as a public portfolio of sanitized security assessment reports. Each report is written in a consultant-style format suitable for technical reviewers, engineering teams, and hiring managers.

🧩 Core Competencies

Domain	Capability
Web Application Security	OWASP-aligned testing, root-cause analysis, remediation planning
Infrastructure Security	Attack-path review, exposure analysis, privilege boundary assessment
Active Directory Security	ADCS risk, trust relationships, identity-focused security assessment
Vulnerability Research	Technical analysis, impact mapping, vendor-style remediation guidance
Security Communication	Executive summaries, business impact, clear defensive recommendations

⭐ Featured Security Reports

Area	Report
Active Directory / ADCS	Cross-Forest Active Directory Penetration Test Report
Web Management Infrastructure	Web Management Platform Penetration Test Report
WordPress / Internal Services	WordPress OCR Platform Penetration Test Report
Support Infrastructure	Support Infrastructure Penetration Test Report
Print Infrastructure	Print Infrastructure Penetration Test Report
Vulnerability Assessment	Apache MINA Deserialization Security Assessment
Vulnerability Assessment	Apache Camel Docling Security Assessment
Browser Security	Chrome V8 Sandbox Security Assessment

📄 Report Structure

Most reports follow a consistent professional format:

1. Title — precise assessment or vulnerability name
2. Executive Summary — non-technical business summary
3. Technical Analysis — root cause and validated risk path, sanitized for publication
4. Impact — technical and business risk assessment
5. Remediation — actionable corrective steps
6. Lessons Learned & Mitigation Strategy — defensive guidance and long-term controls

🧼 Publication Standard

All public reports are sanitized before publication:

• No client-identifying information
• No real credentials, secrets, tokens, or private keys
• No sensitive infrastructure identifiers
• No unnecessary operational artifacts
• Clear placeholders are used where sensitive values were removed

Note

The goal of this portfolio is to demonstrate professional security thinking: identifying risk, explaining impact, and providing practical remediation guidance.