How pushsecurity/saas-attacks works
Project Type and Purpose
• This is an open‐source, content‐centric repository of SaaS attack techniques. It’s not a runnable application or microservice ecosystem; rather, it’s a structured collection of Markdown files intended to be browsed (e.g., via GitHub or a static‐site generator).
• The README describes the “SaaS attacks matrix” and links into individual technique directories under techniques/, each containing description.md and example.md files.
File Structure Analysis
• Top level:
• .gitignore, LICENSE, CONTRIBUTORS.md – standard repo metadata
• README.md – project overview, attack matrix, scope
• techniques/ – primary content directory
• Under techniques/, each subdirectory (e.g., consent_phishing) holds:
• description.md – narrative of the technique
• examples/ – real‐world snippets (e.g., teams.md)
• No src/, no package.json, no config files – implies direct Markdown hosting (GitHub Pages or similar).
README Insights
• Emphasizes inspiration from MITRE ATT&CK but focused on SaaS‐only, networkless attacks
• Provides a matrix table linking categories (Reconnaissance, Initial Access, …) to technique pages
• Invites contributors to add content via issues/PRs
a. Main Components
• Version‐controlled content store – the GitHub repository (Markdown files)
• Content‐build pipeline (optional) – e.g., GitHub Actions + static‐site generator (Jekyll, MkDocs, Hugo)
• Static hosting layer – GitHub Pages, Netlify, or other CDN
• End users – security researchers, red/blue teams, penetration testers browsing the site
• Contribution interface – GitHub Issues/PRs for content updates
b. Relationships & Data Flow
1. Contributor edits or adds Markdown under techniques/ →
2. Git push to main branch → triggers CI pipeline (build step) →
3. Static site generator transforms Markdown into HTML/CSS/JS →
4. Deploy to static host/CDN →
5. End user requests pages via browser → served by CDN →
6. Feedback loop: users file issues/PRs back into the repo
c. Architectural Patterns & Principles
• Content‐as‐Code: storing documentation in VCS, peer review via PRs
• “Build Once, Serve Many”: static‐site generation for performance, security
• Separation of Concerns: content (Markdown) vs. presentation (site theme) vs. deployment (CI/CD)
d. Key Technologies
• Git & GitHub (repo, Issues, PRs)
• Markdown for content authoring
• Static‐site generator of choice (if in use)
• GitHub Actions (CI) or equivalent
• Static hosting/CDN (GitHub Pages, Netlify)