{# Extended Security Architecture Review dashboard: coverage, exceptions, CCM domain conformance, risk disposition, unreviewed/stale projects, recurring root causes, gate decisions, and standards deviation. See web/architecture_dashboard.py for what's real vs. approximated. #} {% from "_macros.html" import info_tip %} Program dashboard
Share of in-scope systems that have at least one successful architecture review.
In scope means every project that has an assessment.
{% endcall %} {{ dash.coverage_pct }}% Coverage — {{ dash.coverage_reviewed }} / {{ dash.coverage_in_scope }} in-scope systemsActive exceptions whose expiry date has already passed.
Close the exception, or record a new one with a later date, to take it off this count.
{% endcall %} {{ dash.exceptions_past_expiry }} Exceptions past expiryFindings a review left as Confirmed where that review is more than {{ past_due_sla_days }} days old.
Findings have no individual due dates, so the review's age stands in for one.
{% endcall %} {{ dash.open_findings_past_due }} Open findings past due (>{{ past_due_sla_days }}d)Findings the review marked Conditional: a fix was proposed, but not confirmed in the code.
Confirm the mitigation in the next review to move them off this count.
{% endcall %} {{ dash.unverified_mitigations }} Unverified mitigationsHow many days nine out of ten assessments take, from start to completion.
One in ten takes longer than this number. A dash means no completed assessment has a duration yet.
{% endcall %} {{ dash.cycle_time_p90_days if dash.cycle_time_p90_days is not none else "—" }} Cycle time p90 (days)Average score per Cloud Controls Matrix domain, taken from each project's latest review.
Hatched bars were not assessed (process-assured or not applicable). That is not a failing score.
{% endcall %}Hatched = not assessed by review (process-assured or not applicable), not a failing score.
What happened to findings across the latest reviews.
Remediated is the drop in finding count between a project's last two reviews. Mitigated is a Conditional verdict. Accepted is an active recorded exception. Open is Confirmed and not yet past due. Past due is Confirmed on a review older than {{ past_due_sla_days }} days.
{% endcall %}Active exceptions grouped by how soon they expire.
Past expiry is already overdue. The other three buckets are still inside 30, 60, and 90 days.
{% endcall %}In-scope projects whose architecture review is missing, stale (latest successful review is over a year old), or whose trust boundaries changed.
The table shows the most recently active of these.
{% endcall %} {% if dash.stale_projects | length > dash.recent_stale_projects | length %} Latest {{ dash.recent_stale_projects | length }} of {{ dash.stale_projects | length }} {% endif %}The most common root causes cited across architecture reviews, including older ones.
A cause that keeps coming back is best fixed once, at platform level, rather than project by project.
{% endcall %} {% if dash.root_causes %}How each project's latest review was gated, from the design verdict in the report.
Approve is a sound design. With conditions can proceed once named fixes land. Reject should not proceed as designed.
{% endcall %}Standards the reviews cite most often as not being met.
A standard high on this list is a candidate for a shared control, rather than a one-off fix in each project.
This card shows the top five. The longer ranking is one click away, and it stops at the top fifteen.
{% endcall %}No standard-specific findings cited yet.
{% endif %}Cloud Controls Matrix domains that no architecture review has assessed yet.
A domain listed here has no score. That is not the same as failing it.
{% endcall %}Every domain has been assessed by at least one review.
{% endif %}