reporting-continuum-security
Report Continuum security
Answer “where do we stand?” with exposure, fix order, impact and decisions, not a findings dump. Read the public AWS CLI evidence and repository, then write a self-contained GitHub-flavoured Markdown report from the template. Use fenced Mermaid diagrams, GFM tables and <details> where they make the report easier to scan.
Fast status path
Keep working until the completed self-check, exact Summary and Markdown path are delivered. Return control early only for a missing environment, profile or region choice, or a fatal read failure needing a decision. Do not ask for a generic “Continue.” Status is read-only toward AWS, source, GitHub and plan decisions; local writes are ignored report files, the local ignore rule and temporary source copies outside the workspace.
- Before every AWS read, read and apply the shared AWS safety prelude, including fresh STS, resolved scope disclosure and
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS=trueon everyawsinvocation. The shared prelude owns credential and optional alias selection; do not add a stricter per-skill rule. Stop on identity failure, unresolved target or endpoint override. Use only public list/get operations. - Create
.continuum/reports/in the target repository as an owner-only directory (umask 077; mkdir -p .continuum/reports; chmod 700 .continuum/reports). Append.continuum/reports/to the repository's local.git/info/excludeif absent; resolve the actual exclude file withgit rev-parse --git-path info/exclude, including in worktrees. Check withgit check-ignore .continuum/reports/security-report.md .continuum/reports/issues.json. If reports are already tracked, stop and ask before writing: ignore rules cannot protect tracked files. Before each write, uselstator an equivalent no-follow check and refuse a symlink at the directory, report or evidence target. Write files underumask 077or explicitly set mode 0600. Never stage this directory or change tracked.gitignorefor status. - List all findings, following every page, saving unchanged responses under
.continuum/reports/. Group by Continuum issue and hydrate selectively as below; do not collect full issue or artifact history. Preserve request start/end times and failures separately. No MCP server or snapshot helper is present. Inspect retained JSON slices without refreshing AWS. - Find current code in the source order below and run the current-code filter. Resolve every Needs review flaw with source and available Git-history evidence before recording Open or Probably fixed, whichever scan found it. Read the confirmed deployment profile to explain components, boundaries and reachability. Record source branch, revision, uncommitted changes, mismatches and assumptions. A report is not an exploit test or deployment verification.
- Fill assets/report-template.md into
.continuum/reports/security-report.md. Replace placeholders; remove empty optional sections.issues.jsoncontains only the deduplicated issue IDs behind reported flaw rows: fetched issue records for Open flaws, compact{ "issueId": "..." }references for others. When exact-code merging combines issues, keep all constituent issue IDs in that one flaw row. Every scoped ID appears in its row. Older repeat counts and unassessed groups belong in Limits without historical ID lists. Attack paths, required fixes and the Validated issues register cover only Open TRUE_POSITIVE flaws. - Complete this self-check against the finished Markdown and retained
issues.json. This is a reasoned review, not an automatic validator. Fix every failed item before delivery: