security-compliance-checker

Extracting OWASP security rules from Excel involves auto-detecting column structures to generate an actionable checklist. This Skill parses user-provided spreadsheets to produce a markdown checklist, driving automated security compliance scans without requiring fixed headers.

Yes, you can scan both backend (.NET) and frontend codebases using a custom Excel security checklist. The process performs phase-driven scans across both architectures, applying your approved rules to generate a consolidated security compliance report.

No, the security rule extractor does not require fixed column headers in the Excel spreadsheet. It features dynamic column detection, automatically identifying and extracting the OWASP checklist structure from your provided file regardless of specific header naming.

Integrating Excel-based OWASP compliance checks into OpenSpec workflows involves script-based execution to generate a markdown checklist. This output enforces established guardrails and security standards, requiring mandatory user approval before applying rules to phase-driven scan plans.

Approving security rules before running a phase-driven code scan requires mandatory user validation. After extracting rules from Excel, the workflow enforces an approval gate where you must explicitly authorize the extracted checklist before generating and executing the scan plan.