Where this offering fits
Security Testing Agent is a software-delivery security enquiry. Select it around required scan types, supported code and the release decisions they must inform. A combined platform should not obscure which engines, integrations and reporting functions the proposed configuration includes.
Architecture and rollout decisions
Map repositories, pipelines and developers responsible for triage. Pilot a known issue through detection, assignment, correction and retest. Agree release thresholds and the owner of exceptions. Source code, build artefacts and credentials must use approved access paths; do not connect a broad repository estate merely to begin an evaluation.
An evaluation scenario for this offering
Choose a bounded development project containing an approved test defect and a known component inventory. Connect only the repositories and pipeline permissions needed for the selected Security Testing Agent evaluation. Follow a build through assessment, finding ownership and the developer’s correction. Introduce a deliberate test-job failure and verify that the release process distinguishes unavailable assessment from a clean result. The final record should include the engines exercised, the evidence reaching the issue owner and the policy for an exception. Success means a usable security decision within the pipeline, not simply a scan job that exits without an obvious error.
Evidence to request for this scope
- List required scan engines and supported technologies.
- Test issue ownership and retest integration.
- Define release exceptions and access boundaries.