@1aboveio/core-skills 0.1.5 → 0.1.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -2
- package/skills/distill-writing/SKILL.md +22 -4
- package/skills/distill-writing/references/extraction.md +19 -3
- package/skills/doc-to-md/SKILL.md +1 -1
- package/skills/editorial-review/SKILL.md +1 -1
- package/skills/house-style/SKILL.md +2 -1
- package/skills/house-style/references/persistence.md +93 -0
- package/skills/house-style/references/rules.md +22 -6
- package/skills/house-style/templates/gap-analysis.md +1 -1
- package/skills/plain-language/SKILL.md +40 -4
- package/skills/polish-cn/SKILL.md +1 -1
- package/skills/reg-parser/SKILL.md +2 -2
- package/skills/reg-parser/scripts/dump_checklist.py +1 -1
- package/skills/terminology/SKILL.md +1 -1
- package/skills/write-doc/SKILL.md +31 -12
- package/skills/write-doc/references/bilingual.md +10 -1
- package/skills/write-doc/references/compliance-reports.md +163 -0
- package/skills/write-doc/references/reports/audit-report-template.md +121 -0
- package/skills/write-doc/references/reports/external-assessment-template.md +183 -0
- package/skills/write-doc/references/reports/management-report-template.md +150 -0
- package/skills/write-doc/references/reports/vars-report-template.md +227 -0
|
@@ -0,0 +1,163 @@
|
|
|
1
|
+
# Compliance reports
|
|
2
|
+
|
|
3
|
+
Use this reference within the `write-doc` workflow when audit findings become a report.
|
|
4
|
+
It replaces the retired `report-writing` skill. For a narrow edit to an existing report, use
|
|
5
|
+
[the edit branch](#edit-an-existing-report) before the full-report steps below.
|
|
6
|
+
Do not repeat the audit or silently change
|
|
7
|
+
its conclusions while writing. The report layouts are retained source layouts, not general
|
|
8
|
+
house-style template skeletons; this reference supplies their inputs, reasoning and checks.
|
|
9
|
+
|
|
10
|
+
## Choose the report
|
|
11
|
+
|
|
12
|
+
| Report | Reader and purpose | Bundled layout |
|
|
13
|
+
| --- | --- | --- |
|
|
14
|
+
| VARS Review Report | Visa and acquirer leadership; Visa Acceptance Risk Standards engagement | [VARS](reports/vars-report-template.md) |
|
|
15
|
+
| Audit Report | Compliance team and internal auditors; technical findings and remediation | [Audit](reports/audit-report-template.md) |
|
|
16
|
+
| External Assessment | Regulators, external auditors and certification bodies; formal submission | [External](reports/external-assessment-template.md) |
|
|
17
|
+
| Management Report | Board, C-suite and risk committee; posture and resource decisions | [Management](reports/management-report-template.md) |
|
|
18
|
+
|
|
19
|
+
Infer the report from the stated audience or purpose. Ask once if neither is clear;
|
|
20
|
+
default to Audit Report for a technical requestor. A VARS engagement always uses the
|
|
21
|
+
VARS layout, not the board or technical alternative. VARS has externally mandated structure;
|
|
22
|
+
ordinary audit, external and management layouts are adaptable defaults. For those reports,
|
|
23
|
+
use the shared house-style selector: an explicit template, then a matching project template,
|
|
24
|
+
then the bundled layout. A project template replaces the bundled structure, not the evidence,
|
|
25
|
+
finding coverage, source ratings or review checks in this reference. Apply house style to prose.
|
|
26
|
+
Use a gap analysis instead for a standalone comparison of requirements and current state
|
|
27
|
+
that is not a report of an assessment.
|
|
28
|
+
|
|
29
|
+
## Edit an existing report
|
|
30
|
+
|
|
31
|
+
A copy-edit that changes no finding, rating, scope, count, recommendation or mandated text
|
|
32
|
+
follows `write-doc`'s narrow-edit workflow. Read the existing report and applicable guidance;
|
|
33
|
+
verify only the passages and facts affected by the change. Do not require the complete tracker
|
|
34
|
+
for an unrelated spelling or formatting correction, re-audit the report, or call the edit a
|
|
35
|
+
new assessment or finalization. Preserve protected text and all unaffected content.
|
|
36
|
+
|
|
37
|
+
An edit that changes a substantive assessment claim requires its supporting source. A new
|
|
38
|
+
report, a request to reassess findings, or a request to finalize a submission uses the full
|
|
39
|
+
evidence and coverage checks below. If a requested change touches mandated wording, surface
|
|
40
|
+
that conflict before changing it; do not silently paraphrase it.
|
|
41
|
+
|
|
42
|
+
## Inputs and evidence
|
|
43
|
+
|
|
44
|
+
Read the full findings file. For a generic assessment, retain each finding's ID, title,
|
|
45
|
+
category, status (Pass / Fail / Partial / N/A), severity (Critical / Major / Minor /
|
|
46
|
+
Observation), observations, evidence and recommendations. Normalize other input shapes
|
|
47
|
+
without inventing missing values. Flag missing status or severity; never turn an unknown
|
|
48
|
+
into Pass or a lower severity. Mark missing evidence as **Evidence Pending**, keeping
|
|
49
|
+
the finding visible. Missing facts follow `write-doc`'s gap rules.
|
|
50
|
+
|
|
51
|
+
Preserve original IDs. Assign `F-001`, `F-002`, and so on only when IDs are absent.
|
|
52
|
+
Link findings to remediation and evidence by ID. Keep source ratings, scales, findings
|
|
53
|
+
and input counts unchanged; house terminology applies to prose, not rating values.
|
|
54
|
+
If an external layout uses another status vocabulary, show its mapping to the source
|
|
55
|
+
values and retain the source values for reconciliation. Do not infer a new rating.
|
|
56
|
+
|
|
57
|
+
For mixed frameworks, organize by framework first, then requirement. State the actual
|
|
58
|
+
scope, period, assessor and framework when supplied. Root causes, financial impacts,
|
|
59
|
+
likelihoods, costs, owners, dates and effort estimates must come from sources or be
|
|
60
|
+
clearly marked proposals or gaps, never copied from layout examples.
|
|
61
|
+
|
|
62
|
+
Count the unit actually present: findings, controls and requirements are not interchangeable.
|
|
63
|
+
A findings-only extract cannot establish the total controls assessed, pass count or overall
|
|
64
|
+
compliance rate. State each percentage's numerator, denominator and treatment of N/A or
|
|
65
|
+
unassessed items. Use an overall rating only when the source supplies it or an authorized
|
|
66
|
+
rubric derives it; otherwise describe the known posture and its limits without a new grade.
|
|
67
|
+
|
|
68
|
+
### VARS gate
|
|
69
|
+
|
|
70
|
+
VARS requires the complete per-control assessment, normally `tracker.md` from
|
|
71
|
+
`compliance-audit` against its VARS checklist or a parsed equivalent from `reg-parser`.
|
|
72
|
+
A summary, verbal findings or a partial sub-domain review is not enough. Verify the
|
|
73
|
+
tracker against the applicable control checklist, not merely a list of headings: all
|
|
74
|
+
nine sub-domains and all in-scope controls must be assessed. If the tracker is absent,
|
|
75
|
+
incomplete or has a sub-domain marked Not Assessed, stop and ask for the complete
|
|
76
|
+
tracker, or offer `compliance-audit` first. Do not draft a final report around that gap.
|
|
77
|
+
|
|
78
|
+
Use the tracker's Control Effectiveness Rating (Satisfactory / Improvement Recommended /
|
|
79
|
+
Unsatisfactory / N/A), not the generic finding severity, for VARS rollups. Flag missing
|
|
80
|
+
ratings or mandatory tracker fields and resolve them before finalizing; do not invent
|
|
81
|
+
generic severities for a VARS tracker that has no severity field. Record the tracker
|
|
82
|
+
filename and version for Section 5 and its companion *VARS Control Testing and
|
|
83
|
+
Remediation Tracking* Excel spreadsheet. Do not claim the Excel exists or is synchronized
|
|
84
|
+
without checking it.
|
|
85
|
+
|
|
86
|
+
## Draft and review
|
|
87
|
+
|
|
88
|
+
Use `write-doc`'s outline, draft, editorial review, fix and delivery steps. Apply the
|
|
89
|
+
nearest WRITING.md from the findings file's directory, or for pasted input the output
|
|
90
|
+
directory, else the working directory, under the shared lookup rules. Never edit it.
|
|
91
|
+
For non-VARS reports, follow the selected template's structure. House style must not change
|
|
92
|
+
scope, ratings or findings. Give editorial-review both the selected layout and the checks
|
|
93
|
+
below, including Additional VARS checks when applicable. The table above supplies the reader
|
|
94
|
+
and purpose (`Use when`); these checks supply the layouts' `Done when`. Review against both,
|
|
95
|
+
not a generic checklist alone.
|
|
96
|
+
|
|
97
|
+
**VARS exception:** ignore WRITING.md for the VARS report. Keep Visa's headings, ordering,
|
|
98
|
+
canonical sub-domains and mandated boilerplate verbatim, including the Purpose,
|
|
99
|
+
reliance statement and recommendation-summary stem. General length limits, terminology,
|
|
100
|
+
translation and editorial advice must not rewrite them. Treat mandated passages as
|
|
101
|
+
locked even where the retained Visa layout presents them as quotations. A requested
|
|
102
|
+
translation is a separate companion, not a replacement Visa deliverable. Never claim
|
|
103
|
+
Visa conducted or approved work unless the sources establish it; stop and resolve any
|
|
104
|
+
conflict between mandated language and the actual assessor or scope before finalizing.
|
|
105
|
+
|
|
106
|
+
Before delivery, check the saved report against the input and selected layout:
|
|
107
|
+
|
|
108
|
+
- **Audit:** every finding has its own section, with evidence, root cause when known,
|
|
109
|
+
risk and remediation. Reconcile all severity and status counts to the source.
|
|
110
|
+
- **External:** map every finding to the actual regulatory requirement and retain
|
|
111
|
+
traceability to the source ID. Unknown mappings stay explicit gaps. Scope, methods,
|
|
112
|
+
limitations and any attestation must match the evidence and assessor authority;
|
|
113
|
+
never fabricate a signature or certification. Distinguish total reviewed, applicable,
|
|
114
|
+
N/A and unassessed items, and reconcile those populations without counting a finding
|
|
115
|
+
as a requirement. Include an attestation only when the authorized assessor's conclusion
|
|
116
|
+
is supplied. Otherwise state that no attestation is provided, without a signature stub.
|
|
117
|
+
- **Management:** lead with at most one page on posture, key risks and decisions.
|
|
118
|
+
Aggregate all categories without losing findings or changing severity counts.
|
|
119
|
+
Explain technical risks in business terms; quantify only supported impacts.
|
|
120
|
+
Without prior data, omit the progress section and note
|
|
121
|
+
"Baseline assessment - no prior data" in methodology.
|
|
122
|
+
- **All reports:** lead with overall posture when there are no critical findings.
|
|
123
|
+
Check all totals and percentages using their source counts and denominator. No
|
|
124
|
+
unresolved layout filler such as `{{...}}`, `____` or `MM/YEAR` may remain in a final
|
|
125
|
+
deliverable. Label unresolved material facts as draft or pending and disclose their
|
|
126
|
+
effect on the conclusion. Do not invent a regulator's submission acceptance criteria
|
|
127
|
+
or claim acceptance, rejection or readiness without the applicable requirements.
|
|
128
|
+
|
|
129
|
+
### Additional VARS checks
|
|
130
|
+
|
|
131
|
+
- Section 3.d has an overall headline and a business-oriented, 2-3 sentence posture
|
|
132
|
+
for every canonical sub-domain. No operational or evidence-document detail.
|
|
133
|
+
- Section 4 has one row per sub-domain in canonical order, including rows without
|
|
134
|
+
adverse findings. Each row takes its worst control rating: Unsatisfactory before
|
|
135
|
+
Improvement Recommended before Satisfactory; N/A only when all controls are N/A.
|
|
136
|
+
No findings alone does not establish Satisfactory without the underlying ratings.
|
|
137
|
+
- If ATPA is in scope, consolidate all ATPA controls into one additional **Third Party
|
|
138
|
+
Agent** row and a corresponding Section 3.d bullet, not the AACQ rows.
|
|
139
|
+
- Section 4 uses an inline observed, finding, comments narrative in the report's own
|
|
140
|
+
words. Evidence-document, clause and sample citations stay in the tracker; lightweight
|
|
141
|
+
control-ID pointers are allowed. Copy Actions Required and Recommendations word for
|
|
142
|
+
word from the tracker's Issue Description, each item on its own line. Close a fully
|
|
143
|
+
Satisfactory row with `No remediation required.`
|
|
144
|
+
- Section 5 identifies the companion tracker. Section 6 uses sourced remediation
|
|
145
|
+
commitments. Use sequential rows 1-9; legacy Regulatory Risk #10 only if the Visa
|
|
146
|
+
engagement lead requests it.
|
|
147
|
+
|
|
148
|
+
## Export checks
|
|
149
|
+
|
|
150
|
+
Markdown is the authored default. Use the brief's path, else WRITING.md's output folder,
|
|
151
|
+
else `{style}-{framework}-{YYYY-MM-DD}.md`; for VARS,
|
|
152
|
+
`vars-review-report-{acquirer}-{YYYY-MM-DD}.md`. Do not invent an assessment date.
|
|
153
|
+
When DOCX or PDF is requested, also render and inspect that output; Markdown alone is
|
|
154
|
+
not the requested export.
|
|
155
|
+
|
|
156
|
+
For VARS Section 4, plain pandoc conversion collapses `<br>` lines inside wide table
|
|
157
|
+
cells. Render each separated line as its own cell paragraph, using a DOCX renderer such
|
|
158
|
+
as `python-docx` or post-processing the conversion. Render labels such as
|
|
159
|
+
`**Actions Required:**` as real bold, not literal asterisks. Shade Compliance Status
|
|
160
|
+
cells green for Satisfactory, amber for Improvement Recommended, red for Unsatisfactory
|
|
161
|
+
and grey for N/A, and use landscape pages for the table. Inspect the rendered file
|
|
162
|
+
to confirm each action and recommendation remains visible on its own line. PDF has
|
|
163
|
+
the same line-break requirement.
|
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
# Audit Report Template
|
|
2
|
+
|
|
3
|
+
Use this structure with [compliance reports](../compliance-reports.md) for the full technical audit report (audience: compliance team).
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Report Metadata
|
|
8
|
+
|
|
9
|
+
| Field | Value |
|
|
10
|
+
|---|---|
|
|
11
|
+
| Report Title | {Framework} Compliance Audit Report |
|
|
12
|
+
| Assessment Period | {Start Date} – {End Date} |
|
|
13
|
+
| Report Date | {YYYY-MM-DD} |
|
|
14
|
+
| Assessor(s) | {Name(s), Role(s)} |
|
|
15
|
+
| Framework / Standard | {e.g., SOC 2 Type II, ISO 27001, PCI DSS v4.0} |
|
|
16
|
+
| Scope | {Systems, processes, and data in scope} |
|
|
17
|
+
| Classification | {Confidential / Internal / Restricted} |
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## 1. Executive Summary
|
|
22
|
+
|
|
23
|
+
Brief overview (1–2 paragraphs) of the audit scope, approach, and headline results.
|
|
24
|
+
|
|
25
|
+
### Finding Summary
|
|
26
|
+
|
|
27
|
+
| Severity | Count | % of Total |
|
|
28
|
+
|---|---|---|
|
|
29
|
+
| 🔴 Critical | {n} | {%} |
|
|
30
|
+
| 🟠 Major | {n} | {%} |
|
|
31
|
+
| 🟡 Minor | {n} | {%} |
|
|
32
|
+
| 🔵 Observation | {n} | {%} |
|
|
33
|
+
| **Total** | **{n}** | **100%** |
|
|
34
|
+
|
|
35
|
+
### Overall Compliance Posture
|
|
36
|
+
|
|
37
|
+
{One sentence: e.g., "The organization demonstrates a mature control environment with
|
|
38
|
+
two critical gaps requiring immediate remediation."}
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
## 2. Findings
|
|
43
|
+
|
|
44
|
+
Repeat this block for each finding, ordered by severity (Critical → Observation).
|
|
45
|
+
|
|
46
|
+
### F-{NNN}: {Finding Title}
|
|
47
|
+
|
|
48
|
+
| Field | Detail |
|
|
49
|
+
|---|---|
|
|
50
|
+
| **ID** | F-{NNN} |
|
|
51
|
+
| **Category** | {e.g., Access Control} |
|
|
52
|
+
| **Control Reference** | {e.g., CC6.1, A.9.2.3} |
|
|
53
|
+
| **Status** | {Source status, including Pass / Fail / Partial / N/A} |
|
|
54
|
+
| **Severity** | {Critical / Major / Minor / Observation} |
|
|
55
|
+
|
|
56
|
+
**Observation:**
|
|
57
|
+
{Detailed description of what was found. Reference specific systems, configurations,
|
|
58
|
+
or processes. Be precise — include paths, parameter names, versions where relevant.}
|
|
59
|
+
|
|
60
|
+
**Evidence:**
|
|
61
|
+
{Reference evidence items: E-001, E-002. Describe what each evidence item shows.
|
|
62
|
+
Full evidence in Appendix A.}
|
|
63
|
+
|
|
64
|
+
**Root Cause:**
|
|
65
|
+
{Why the gap exists. Distinguish between process failure, technical misconfiguration,
|
|
66
|
+
resource constraint, or design gap.}
|
|
67
|
+
|
|
68
|
+
**Risk:**
|
|
69
|
+
{Impact if unaddressed. Quantify where possible: number of records exposed,
|
|
70
|
+
blast radius, regulatory penalty exposure.}
|
|
71
|
+
|
|
72
|
+
**Recommendation:**
|
|
73
|
+
{Specific remediation steps.}
|
|
74
|
+
|
|
75
|
+
| Priority | Timeline | Estimated Effort | Owner |
|
|
76
|
+
|---|---|---|---|
|
|
77
|
+
| {P1/P2/P3} | {e.g., 30 days} | {e.g., 2 engineer-weeks} | {Role/Team} |
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## 3. Remediation Plan
|
|
82
|
+
|
|
83
|
+
Consolidated view of all findings requiring action, sorted by priority.
|
|
84
|
+
|
|
85
|
+
| ID | Title | Severity | Priority | Timeline | Owner | Status |
|
|
86
|
+
|---|---|---|---|---|---|---|
|
|
87
|
+
| F-001 | {Title} | 🔴 Critical | P1 | 14 days | {Owner} | Open |
|
|
88
|
+
| F-002 | {Title} | 🟠 Major | P2 | 30 days | {Owner} | Open |
|
|
89
|
+
| ... | | | | | | |
|
|
90
|
+
|
|
91
|
+
---
|
|
92
|
+
|
|
93
|
+
## Appendix A: Evidence Index
|
|
94
|
+
|
|
95
|
+
| Evidence ID | Description | Type | Source | Date Collected |
|
|
96
|
+
|---|---|---|---|---|
|
|
97
|
+
| E-001 | {Description} | {Screenshot / Log / Config / Interview} | {System/Person} | {Date} |
|
|
98
|
+
| E-002 | {Description} | {Type} | {Source} | {Date} |
|
|
99
|
+
|
|
100
|
+
{Include raw evidence below or attach as separate files.}
|
|
101
|
+
|
|
102
|
+
### E-001: {Description}
|
|
103
|
+
|
|
104
|
+
```
|
|
105
|
+
{Raw evidence: log excerpt, configuration snippet, or screenshot reference}
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
---
|
|
109
|
+
|
|
110
|
+
## Appendix B: Assessment Methodology
|
|
111
|
+
|
|
112
|
+
{Describe the audit approach: document review, technical testing, interviews,
|
|
113
|
+
sampling methodology, tools used.}
|
|
114
|
+
|
|
115
|
+
---
|
|
116
|
+
|
|
117
|
+
## Appendix C: Glossary
|
|
118
|
+
|
|
119
|
+
| Term | Definition |
|
|
120
|
+
|---|---|
|
|
121
|
+
| {Term} | {Definition} |
|
|
@@ -0,0 +1,183 @@
|
|
|
1
|
+
# External Assessment Template
|
|
2
|
+
|
|
3
|
+
Use this structure with [compliance reports](../compliance-reports.md) for regulatory or external auditor submissions (audience: regulators,
|
|
4
|
+
certification bodies, external auditors).
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Cover Page
|
|
9
|
+
|
|
10
|
+
| Field | Value |
|
|
11
|
+
|---|---|
|
|
12
|
+
| Document Title | {Framework} Compliance Assessment Report |
|
|
13
|
+
| Prepared For | {Regulatory body / Certification body / Client name} |
|
|
14
|
+
| Prepared By | {Assessor organization, qualifications} |
|
|
15
|
+
| Assessment Period | {Start Date} – {End Date} |
|
|
16
|
+
| Report Date | {YYYY-MM-DD} |
|
|
17
|
+
| Document Version | {e.g., 1.0} |
|
|
18
|
+
| Classification | {Confidential} |
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## 1. Scope Statement
|
|
23
|
+
|
|
24
|
+
### 1.1 Purpose
|
|
25
|
+
|
|
26
|
+
{State the purpose of the assessment. Reference the specific regulation, standard, or
|
|
27
|
+
contractual obligation that mandates this assessment.}
|
|
28
|
+
|
|
29
|
+
Example: "This assessment evaluates [Organization]'s compliance with [Regulation/Standard]
|
|
30
|
+
as required under [Article/Section]. The assessment covers [systems/processes/data]
|
|
31
|
+
within the defined scope boundary."
|
|
32
|
+
|
|
33
|
+
### 1.2 Scope Boundary
|
|
34
|
+
|
|
35
|
+
{Define what is in scope and out of scope. Be explicit about:}
|
|
36
|
+
- Systems and applications assessed
|
|
37
|
+
- Business processes covered
|
|
38
|
+
- Data types and classifications included
|
|
39
|
+
- Geographic locations
|
|
40
|
+
- Third-party dependencies included/excluded
|
|
41
|
+
|
|
42
|
+
### 1.3 Assessment Period
|
|
43
|
+
|
|
44
|
+
{The time window covered by this assessment.}
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## 2. Assessment Methodology
|
|
49
|
+
|
|
50
|
+
### 2.1 Approach
|
|
51
|
+
|
|
52
|
+
{Describe the methodology: control testing, evidence review, interviews, technical
|
|
53
|
+
validation. Reference any recognized assessment framework used (e.g., ISAE 3402,
|
|
54
|
+
AICPA Trust Services Criteria).}
|
|
55
|
+
|
|
56
|
+
### 2.2 Sampling
|
|
57
|
+
|
|
58
|
+
{Describe sampling methodology and rationale. State sample sizes and selection criteria.}
|
|
59
|
+
|
|
60
|
+
### 2.3 Limitations
|
|
61
|
+
|
|
62
|
+
{State any limitations, caveats, or constraints that affected the assessment.}
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## 3. Compliance Status by Requirement
|
|
67
|
+
|
|
68
|
+
Retain source statuses and severities, including Observation and N/A. The alternatives
|
|
69
|
+
below are examples, not a new rating scale. If the destination mandates different labels,
|
|
70
|
+
show the mapping and retain source values for reconciliation. Never replace an unknown
|
|
71
|
+
requirement with an invented legal citation.
|
|
72
|
+
|
|
73
|
+
Organize by regulation article or standard control domain. Each requirement gets a
|
|
74
|
+
status determination with supporting rationale.
|
|
75
|
+
|
|
76
|
+
### 3.1 {Requirement Domain / Article}
|
|
77
|
+
|
|
78
|
+
#### {Article/Section Number}: {Requirement Title}
|
|
79
|
+
|
|
80
|
+
| Field | Detail |
|
|
81
|
+
|---|---|
|
|
82
|
+
| **Requirement** | {Full text or summary of the regulatory requirement} |
|
|
83
|
+
| **Regulation Reference** | {e.g., Article 32(1)(a), Regulation (EU) 2016/679} |
|
|
84
|
+
| **Compliance Status** | {Compliant / Partially Compliant / Non-Compliant / Not Applicable} |
|
|
85
|
+
| **Severity of Gap** | {Source severity, including Critical / Major / Minor / Observation / N/A} |
|
|
86
|
+
|
|
87
|
+
**Assessment Rationale:**
|
|
88
|
+
{Explain the basis for the status determination. Reference specific controls observed,
|
|
89
|
+
evidence reviewed, and tests performed.}
|
|
90
|
+
|
|
91
|
+
**Identified Gaps:**
|
|
92
|
+
{If not fully compliant, describe each gap precisely. Reference the specific
|
|
93
|
+
sub-requirement that is not met.}
|
|
94
|
+
|
|
95
|
+
**Recommended Remediation:**
|
|
96
|
+
{Steps to achieve compliance. Reference industry best practices or regulatory guidance.}
|
|
97
|
+
|
|
98
|
+
{Repeat for each requirement/article.}
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
## 4. Gap Analysis Matrix
|
|
103
|
+
|
|
104
|
+
Summary view mapping each requirement to its compliance status.
|
|
105
|
+
|
|
106
|
+
| Requirement | Reference | Status | Severity | Remediation Target |
|
|
107
|
+
|---|---|---|---|---|
|
|
108
|
+
| {Requirement title} | {Article/Section} | {Status} | {Severity} | {Target date} |
|
|
109
|
+
| {Requirement title} | {Article/Section} | {Status} | {Severity} | {Target date} |
|
|
110
|
+
|
|
111
|
+
### Summary Statistics
|
|
112
|
+
|
|
113
|
+
Count requirements only when the input establishes that population; otherwise label
|
|
114
|
+
these as finding counts. State the denominator for percentages and whether N/A is
|
|
115
|
+
excluded from the applicable population. Keep unassessed items visible rather than
|
|
116
|
+
counting them as compliant or N/A.
|
|
117
|
+
|
|
118
|
+
| Status | Count | Percentage |
|
|
119
|
+
|---|---|---|
|
|
120
|
+
| Compliant | {n} | {%} |
|
|
121
|
+
| Partially Compliant | {n} | {%} |
|
|
122
|
+
| Non-Compliant | {n} | {%} |
|
|
123
|
+
| Not Applicable | {n} | {%} |
|
|
124
|
+
|
|
125
|
+
---
|
|
126
|
+
|
|
127
|
+
## 5. Remediation Roadmap
|
|
128
|
+
|
|
129
|
+
| Priority | Requirement | Gap Description | Recommended Action | Target Date | Effort Estimate |
|
|
130
|
+
|---|---|---|---|---|---|
|
|
131
|
+
| P1 | {Ref} | {Gap} | {Action} | {Date} | {Estimate} |
|
|
132
|
+
| P2 | {Ref} | {Gap} | {Action} | {Date} | {Estimate} |
|
|
133
|
+
|
|
134
|
+
---
|
|
135
|
+
|
|
136
|
+
## 6. Attestation Statement
|
|
137
|
+
|
|
138
|
+
Use the wording below only when the authorized assessor supplied that conclusion and
|
|
139
|
+
the engagement calls for attestation. Otherwise state that no attestation is provided;
|
|
140
|
+
do not invent credentials, a signature, an overall rating or approval. The stem is
|
|
141
|
+
adaptable, not locked. Reconcile source populations, including N/A and unassessed items.
|
|
142
|
+
|
|
143
|
+
> Based on the assessment conducted during the period {Start Date} to {End Date},
|
|
144
|
+
> applying the methodology described in Section 2, and having reviewed the evidence
|
|
145
|
+
> documented herein, {Assessor Organization} [attests/concludes] the following:
|
|
146
|
+
>
|
|
147
|
+
> {Organization} has demonstrated {[full/substantial/partial]} compliance with
|
|
148
|
+
> {Regulation/Standard} within the defined scope.
|
|
149
|
+
>
|
|
150
|
+
> {Number} requirements were reviewed: {n} were assessed as fully compliant,
|
|
151
|
+
> {n} partially compliant, {n} non-compliant, {n} not applicable, and {n} unassessed.
|
|
152
|
+
> Of the {n} applicable requirements, {n} were assessed. {State the denominator for any rate.}
|
|
153
|
+
>
|
|
154
|
+
> The findings documented in this report represent the compliance posture as of
|
|
155
|
+
> {Report Date}. This attestation does not guarantee future compliance.
|
|
156
|
+
>
|
|
157
|
+
> **Assessor:** {Name, Title, Qualification}
|
|
158
|
+
> **Date:** {YYYY-MM-DD}
|
|
159
|
+
> **Signature:** {Supplied authorized signature, only when provided}
|
|
160
|
+
|
|
161
|
+
---
|
|
162
|
+
|
|
163
|
+
## Appendix A: Evidence Index
|
|
164
|
+
|
|
165
|
+
| Evidence ID | Description | Requirement Ref | Type | Date |
|
|
166
|
+
|---|---|---|---|---|
|
|
167
|
+
| E-001 | {Description} | {Article/Section} | {Type} | {Date} |
|
|
168
|
+
|
|
169
|
+
---
|
|
170
|
+
|
|
171
|
+
## Appendix B: Assessor Qualifications
|
|
172
|
+
|
|
173
|
+
| Assessor | Qualifications | Role in Assessment |
|
|
174
|
+
|---|---|---|
|
|
175
|
+
| {Name} | {e.g., CISA, CISSP, ISO 27001 Lead Auditor} | {Lead Assessor / Technical Reviewer} |
|
|
176
|
+
|
|
177
|
+
---
|
|
178
|
+
|
|
179
|
+
## Appendix C: Document Control
|
|
180
|
+
|
|
181
|
+
| Version | Date | Author | Changes |
|
|
182
|
+
|---|---|---|---|
|
|
183
|
+
| 1.0 | {Date} | {Author} | Initial release |
|
|
@@ -0,0 +1,150 @@
|
|
|
1
|
+
# Management Report Template
|
|
2
|
+
|
|
3
|
+
Use this structure with [compliance reports](../compliance-reports.md) for leadership and board-level reporting (audience: C-suite, board,
|
|
4
|
+
risk committee).
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Report Metadata
|
|
9
|
+
|
|
10
|
+
| Field | Value |
|
|
11
|
+
|---|---|
|
|
12
|
+
| Report Title | Compliance Posture — {Framework} Assessment |
|
|
13
|
+
| Report Date | {YYYY-MM-DD} |
|
|
14
|
+
| Assessment Period | {Start Date} – {End Date} |
|
|
15
|
+
| Prepared By | {Compliance Team / Assessor} |
|
|
16
|
+
| Classification | {Confidential — Board Distribution} |
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
## 1. Executive Summary
|
|
21
|
+
|
|
22
|
+
{One page maximum. This section stands alone — a reader should understand the
|
|
23
|
+
organization's compliance posture without reading further.}
|
|
24
|
+
|
|
25
|
+
**Overall Compliance Posture:** {Source rating, or a narrative conclusion limited to the evidence}
|
|
26
|
+
|
|
27
|
+
Do not introduce an overall scale unless the source or an authorized rubric defines it.
|
|
28
|
+
A findings-only extract does not establish the full assessment posture or pass rate.
|
|
29
|
+
In the headline figures below, use only populations the source supplies; omit an unknown
|
|
30
|
+
control total or compliance percentage and explain that limit instead.
|
|
31
|
+
|
|
32
|
+
**Headline Numbers:**
|
|
33
|
+
- **{N}** controls assessed across **{N}** categories
|
|
34
|
+
- **{N}%** fully compliant
|
|
35
|
+
- **{N}** critical gaps requiring immediate action
|
|
36
|
+
- **{N}** major gaps requiring near-term remediation
|
|
37
|
+
|
|
38
|
+
**Key Message:**
|
|
39
|
+
{2–3 sentences summarizing the most important takeaway. Focus on business risk, not
|
|
40
|
+
technical details. Example: "Two critical gaps in access management expose the
|
|
41
|
+
organization to regulatory penalty risk estimated at $X–$Y. Remediation requires
|
|
42
|
+
approximately N engineer-weeks and should begin immediately."}
|
|
43
|
+
|
|
44
|
+
**Immediate Actions Required:**
|
|
45
|
+
1. {Action 1 — one line, business language}
|
|
46
|
+
2. {Action 2}
|
|
47
|
+
3. {Action 3}
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
## 2. Risk Heatmap
|
|
52
|
+
|
|
53
|
+
Findings by severity and category. Use this to identify concentration areas.
|
|
54
|
+
|
|
55
|
+
| Category | 🔴 Critical | 🟠 Major | 🟡 Minor | 🔵 Observation | Total |
|
|
56
|
+
|---|---|---|---|---|---|
|
|
57
|
+
| Access Control | {n} | {n} | {n} | {n} | {n} |
|
|
58
|
+
| Data Protection | {n} | {n} | {n} | {n} | {n} |
|
|
59
|
+
| Incident Response | {n} | {n} | {n} | {n} | {n} |
|
|
60
|
+
| Change Management | {n} | {n} | {n} | {n} | {n} |
|
|
61
|
+
| Vendor Management | {n} | {n} | {n} | {n} | {n} |
|
|
62
|
+
| {Other categories} | | | | | |
|
|
63
|
+
| **Total** | **{n}** | **{n}** | **{n}** | **{n}** | **{n}** |
|
|
64
|
+
|
|
65
|
+
**Concentration Risk:**
|
|
66
|
+
{Identify categories with multiple critical/major findings. Example: "Access Control
|
|
67
|
+
accounts for 60% of critical findings, indicating a systemic control weakness."}
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
## 3. Business Impact Analysis
|
|
72
|
+
|
|
73
|
+
For each critical and major finding, translate technical risk into business terms.
|
|
74
|
+
|
|
75
|
+
### 3.1 {Finding Category / Theme}
|
|
76
|
+
|
|
77
|
+
**What's at risk:**
|
|
78
|
+
{Business impact in plain language. Examples: customer data exposure, regulatory fine,
|
|
79
|
+
operational disruption, reputational damage, contract breach.}
|
|
80
|
+
|
|
81
|
+
**Quantified impact (where estimable):**
|
|
82
|
+
- Regulatory penalty exposure: {$X – $Y}
|
|
83
|
+
- Potential data records affected: {N}
|
|
84
|
+
- Operational downtime risk: {hours/days}
|
|
85
|
+
- Contract/SLA breach exposure: {description}
|
|
86
|
+
|
|
87
|
+
**Likelihood:** {High / Medium / Low}
|
|
88
|
+
|
|
89
|
+
{Repeat for each significant impact area.}
|
|
90
|
+
|
|
91
|
+
---
|
|
92
|
+
|
|
93
|
+
## 4. Recommended Actions
|
|
94
|
+
|
|
95
|
+
Prioritized actions with effort and cost estimates. Designed for resource allocation decisions.
|
|
96
|
+
|
|
97
|
+
| # | Action | Addresses | Priority | Effort | Cost Estimate | Suggested Owner | Target Date |
|
|
98
|
+
|---|---|---|---|---|---|---|---|
|
|
99
|
+
| 1 | {Action description} | {Finding refs} | 🔴 Immediate | {e.g., 3 weeks} | {$X} | {Role/Dept} | {Date} |
|
|
100
|
+
| 2 | {Action description} | {Finding refs} | 🟠 Near-term | {e.g., 6 weeks} | {$X} | {Role/Dept} | {Date} |
|
|
101
|
+
| 3 | {Action description} | {Finding refs} | 🟡 Planned | {e.g., Q3} | {$X} | {Role/Dept} | {Date} |
|
|
102
|
+
|
|
103
|
+
**Total estimated remediation investment:** {$X over N months}
|
|
104
|
+
|
|
105
|
+
---
|
|
106
|
+
|
|
107
|
+
## 5. Progress Since Last Assessment
|
|
108
|
+
|
|
109
|
+
{Include only when prior assessment data is available. If this is a baseline assessment,
|
|
110
|
+
state: "This is the initial baseline assessment. Progress tracking begins with the
|
|
111
|
+
next assessment cycle."}
|
|
112
|
+
|
|
113
|
+
### Trend Summary
|
|
114
|
+
|
|
115
|
+
| Metric | Prior ({Date}) | Current | Change |
|
|
116
|
+
|---|---|---|---|
|
|
117
|
+
| Overall compliance rate | {%} | {%} | {↑/↓ Δ%} |
|
|
118
|
+
| Critical findings | {n} | {n} | {↑/↓ Δn} |
|
|
119
|
+
| Major findings | {n} | {n} | {↑/↓ Δn} |
|
|
120
|
+
| Open remediation items | {n} | {n} | {↑/↓ Δn} |
|
|
121
|
+
|
|
122
|
+
### Remediation Closure Rate
|
|
123
|
+
|
|
124
|
+
- Items from prior assessment: {N}
|
|
125
|
+
- Closed / remediated: {N} ({%})
|
|
126
|
+
- Still open: {N}
|
|
127
|
+
- New findings this cycle: {N}
|
|
128
|
+
|
|
129
|
+
### Notable Improvements
|
|
130
|
+
|
|
131
|
+
{Bullet list of specific improvements since the last assessment.}
|
|
132
|
+
|
|
133
|
+
### Persistent Gaps
|
|
134
|
+
|
|
135
|
+
{Findings that remain open from the prior assessment, with explanation of delays.}
|
|
136
|
+
|
|
137
|
+
---
|
|
138
|
+
|
|
139
|
+
## 6. Appendix
|
|
140
|
+
|
|
141
|
+
### Methodology Note
|
|
142
|
+
|
|
143
|
+
{Brief description of assessment approach, framework used, and scope. Keep to one
|
|
144
|
+
paragraph — detailed methodology is in the full audit report.}
|
|
145
|
+
|
|
146
|
+
### Detailed Data Reference
|
|
147
|
+
|
|
148
|
+
{Reference to the full Audit Report for technical details: "For complete finding
|
|
149
|
+
details, evidence, and technical remediation steps, refer to the Audit Report
|
|
150
|
+
dated {Date}."}
|