You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ make dynamic-fast
13
13
make findings-full
14
14
make release-full
15
15
make lifecycle-full
16
+
make evidence-full
16
17
```
17
18
18
19
Use deterministic synthetic data only. Do not add real patient, NHS, genomic, credential, or cloud account data.
@@ -29,3 +30,4 @@ Use deterministic synthetic data only. Do not add real patient, NHS, genomic, cr
29
30
- Keep findings IDs deterministic and avoid absolute local paths, raw JWTs, private keys or real data in canonical findings outputs.
30
31
- Keep release-gate evidence deterministic. Use `make release-gate-enforce` only when you intentionally want enforcement exit codes; evidence-mode release targets must still run for block and conditional decisions.
31
32
- Keep lifecycle evidence deterministic. Scanner suppressions may inform lifecycle records, but only security exceptions under `config/lifecycle/` and `outputs/security/lifecycle/` may support risk acceptance or deferral.
33
+
- Keep consolidated evidence deterministic. Update `config/evidence/source-registry.yaml` when adding a source domain, and do not add reports with manually maintained counts.
Copy file name to clipboardExpand all lines: README.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ Milestone 8 adds risk-based release gates over the Milestone 7 canonical finding
34
34
35
35
Milestone 9 adds deterministic vulnerability lifecycle and exception governance over canonical findings and release outputs. It produces a vulnerability register, lifecycle history, security exception register, expiry reports, verification evidence, audit reports and a pinned lifecycle workflow. It does not start Security Champions, deploy, push containers, create AWS resources, commit or push.
36
36
37
+
Milestone 10 adds consolidated security evidence and reporting across Milestones 1-9. It produces a deterministic evidence bundle, source lineage, control coverage, security metrics, integrity summaries and audience-oriented reports. It does not start Milestone 11 developer enablement, Security Champions, dashboards, ticketing, external reporting, deployment or AWS resource creation.
38
+
37
39
## Milestone 1 Scope
38
40
39
41
Implemented:
@@ -143,6 +145,19 @@ Implemented as local governance, evidence and reports:
143
145
144
146
Not implemented in Milestone 9: Security Champions, production ticketing integration, deployment approvals, artefact signing/provenance, AWS deployment, container push or production vulnerability-management operations.
145
147
148
+
## Milestone 10 Scope
149
+
150
+
Implemented as local evidence aggregation and reports:
151
+
152
+
- Explicit source registry for threat model, API security, infrastructure, AppSec, dynamic security, findings, release assurance and lifecycle evidence.
153
+
- Deterministic consolidated evidence bundle and manifest.
154
+
- Evidence lineage, control coverage, metrics and integrity summaries.
155
+
- Executive, product-security, engineering and audit reports.
156
+
- Sensitive-content validation for consolidated outputs.
157
+
- A security-evidence CI workflow with minimal permissions and no AWS credentials.
158
+
159
+
Not implemented in Milestone 10: Milestone 11 developer enablement, Security Champions, dashboards, ticketing, external reporting systems, regulatory certification, AWS deployment or production monitoring.
160
+
146
161
## API Capabilities
147
162
148
163
-`GET /health`
@@ -230,6 +245,13 @@ Open `http://127.0.0.1:8000/docs` for FastAPI's local OpenAPI UI.
230
245
-`make verify-lifecycle-evidence`: verify lifecycle evidence checksums and determinism.
Copy file name to clipboardExpand all lines: SECURITY.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ If you identify a vulnerability or unsafe pattern in this demonstration code, op
6
6
7
7
Do not submit real patient data, NHS data, genomic data, credentials, cloud account identifiers, or sensitive operational details in reports.
8
8
9
-
Current implemented security controls include local JWT authentication, role-based and object-level authorisation, threat-model validation, non-deployed Terraform reference controls, a Milestone 5 AppSec pipeline, Milestone 6 local dynamic API security validation, Milestone 7 canonical findings normalisation, Milestone 8 local release-assurance gates, and Milestone 9 vulnerability lifecycle and exception governance.
9
+
Current implemented security controls include local JWT authentication, role-based and object-level authorisation, threat-model validation, non-deployed Terraform reference controls, a Milestone 5 AppSec pipeline, Milestone 6 local dynamic API security validation, Milestone 7 canonical findings normalisation, Milestone 8 local release-assurance gates, Milestone 9 vulnerability lifecycle and exception governance, and Milestone 10 consolidated security evidence reporting.
10
10
11
11
Run local security checks with:
12
12
@@ -17,6 +17,7 @@ make dynamic-fast
17
17
make findings-full
18
18
make release-full
19
19
make lifecycle-full
20
+
make evidence-full
20
21
```
21
22
22
-
Docker-backed Gitleaks, Trivy, Schemathesis and ZAP scans require a running Docker daemon when native binaries or scanner containers are used. Dynamic scan targets must remain local-only. Do not treat local scanner, findings, releaseor lifecycle evidence as a production vulnerability-management programme, penetration test, deployment approval system or Security Champions programme.
23
+
Docker-backed Gitleaks, Trivy, Schemathesis and ZAP scans require a running Docker daemon when native binaries or scanner containers are used. Dynamic scan targets must remain local-only. Do not treat local scanner, findings, release, lifecycle or consolidated evidence as a production vulnerability-management programme, penetration test, deployment approval system, regulatory certification or Security Champions programme.
0 commit comments