How yogikortisa/product-security-engineering works
Main Components
• Document Categories as Primary Modules:
• DevSecOps (including Risk Assessment, Secure Configuration, Attack Surface Management, Vulnerability Disclosure)
• Gap Analysis (with verification standards and toolkits)
• Roadmap (strategic planning documents such as security roadmap spreadsheets)
• Secure SDLC (further split into subdomains like Governance, Design, Implementation, Verification, and Operations)
• Starter Guide (getting-started materials, e.g., OWASP Quick Start Guide)
• Vulnerability Management (related guides on managing and assessing vulnerabilities)
Relationships and Interactions
• Since this resource repository is organized around security program domains, distinguish the flow between high-level strategy/guidelines and their practical execution:
• DevSecOps and Secure SDLC indicate procedural and technical control processes that overlap (for instance, secure configuration in deploy and secure build processes in implementation).
• Gap Analysis feeds into both the Roadmap and Secure SDLC by identifying areas for improvement.
• The Starter Guide provides an entry point; it is the “on-ramp” that connects to more detailed procedures in the other modules.
• Vulnerability Management works as a continuous feedback loop into both DevSecOps (monitoring) and Secure SDLC (verification and operations).
Architectural Patterns and Design Principles
• Modularity and Separation of Concerns: Each high-level directory represents a loosely-coupled module with its own responsibilities.
• Lifecycle Orientation: Especially with Secure SDLC, which is subdivided by different phases of the software/product lifecycle – from governance and design to implementation, verification, and operations.
• Integration Points: Identify key interfaces where components interact (for example, secure configuration documents in DevSecOps connect with implementation practices in Secure SDLC).
Relevant Technologies, Frameworks, or Libraries
• Though this repository does not include executable code, it references a lot of frameworks, guides, and industry standards:
• OWASP ASVS for security requirements.
• OpenScap, Ansible, and other automation tools mentioned in documentation for secure configurations.
• BSSN (the Indonesian Cyber Security Agency) standards and guidelines appear repeatedly, indicating reliance on national or regional security frameworks.
• File formats (Excel, PDF, DOCX, PPTX) suggest that the repository is designed for manual review and use in a variety of environments.