pentest-agent-ci

Validating pentest configurations in a CI/CD pipeline involves checking security assessment scopes and tool catalogs against strict policies. This skill automates that by enforcing fail-closed execution logic and local-first, read-only access to repository configuration files before any pipeline execution occurs.

Fail-closed execution logic for automated security assessments means the pipeline halts if policy validation fails. This skill ensures safety by automatically verifying that dangerous categories like phishing or credential stuffing are disabled and blocking pull requests that violate security policies.

Yes, you can use this skill to gate pull requests for unauthorized pentest scope changes. It performs comprehensive integrity auditing on scope files, skill frontmatter, and catalog schemas to prevent risky operations, ensuring no configuration changes expose sensitive data before deployment.

To prevent dangerous attack categories like phishing from running in automated pentest agents, you apply policy enforcement during the CI/CD validation phase. This skill automatically checks configurations to verify that high-risk categories are disabled and that the agent maintains a strict fail-closed state.

No, validating security pipelines with this skill does not require network access or external dependencies. It operates using local-first, read-only access to repository configuration files, ensuring that your security assessment validation remains isolated and strictly adheres to fail-closed execution logic.

The limitations of automated policy enforcement for pentest pipelines include strict dependency on local-first, read-only repository files. Because it applies fail-closed logic, any unverified or unauthorized configuration changes will halt the pipeline, requiring manual intervention to correct scope definitions or tool catalog schemas.