# Illustrative security project report

Cyber Agoge — teaching example. Fictional scenario and simulated results. Not a student submission, exam answer or measured security assessment.

## Finding
The delivery workflow can publish the application even when a dependency check reports a finding above the agreed threshold.

## Scope and risk
Fictional training application and its delivery workflow. A detected vulnerable dependency could reach a release.

## Proposed defence
Require the security check to pass before publishing. Review workflow changes. Update the dependency. Define the threshold and exception process for the project.

## Validation plan
- Vulnerable dependency: the check fails and the release stays blocked.
- Updated dependency: the check passes and the release may proceed.
- Unavailable check: the release stays blocked.

These are illustrative expectations, not executed tests. In your own work, attach actual run URLs, commit identifiers and test outputs.

## Limitations
A passing dependency check does not establish that the application is secure. Test application behaviour, access controls and AI features separately.

Programme: https://www.cyberagoge.com/bootcamp/