@elnora-ai/linear 1.0.1 → 1.1.0
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/.claude-plugin/marketplace.json +7 -2
- package/.claude-plugin/plugin.json +1 -1
- package/CHANGELOG.md +13 -1
- package/README.md +116 -26
- package/agents/linear-issue-creator.md +129 -17
- package/agents/linear-issue-reviewer.md +122 -23
- package/agents/linear-issue-updater.md +137 -25
- package/agents/linear-state-curator.md +173 -0
- package/agents/linear-url-to-issues.md +189 -26
- package/commands/linear-cleanup.md +64 -29
- package/dist/cli.js +64 -1
- package/dist/cli.js.map +1 -1
- package/dist/client/auth.d.ts.map +1 -1
- package/dist/client/auth.js +13 -2
- package/dist/client/auth.js.map +1 -1
- package/dist/client/linear-client.d.ts +7 -0
- package/dist/client/linear-client.d.ts.map +1 -1
- package/dist/client/linear-client.js +13 -1
- package/dist/client/linear-client.js.map +1 -1
- package/dist/commands/agent-activities.d.ts +3 -0
- package/dist/commands/agent-activities.d.ts.map +1 -0
- package/dist/commands/agent-activities.js +144 -0
- package/dist/commands/agent-activities.js.map +1 -0
- package/dist/commands/agent-sessions.d.ts +3 -0
- package/dist/commands/agent-sessions.d.ts.map +1 -0
- package/dist/commands/agent-sessions.js +132 -0
- package/dist/commands/agent-sessions.js.map +1 -0
- package/dist/commands/attachments.d.ts +3 -0
- package/dist/commands/attachments.d.ts.map +1 -0
- package/dist/commands/attachments.js +265 -0
- package/dist/commands/attachments.js.map +1 -0
- package/dist/commands/audit.d.ts +3 -0
- package/dist/commands/audit.d.ts.map +1 -0
- package/dist/commands/audit.js +73 -0
- package/dist/commands/audit.js.map +1 -0
- package/dist/commands/comments.d.ts +3 -0
- package/dist/commands/comments.d.ts.map +1 -0
- package/dist/commands/comments.js +107 -0
- package/dist/commands/comments.js.map +1 -0
- package/dist/commands/completion.d.ts +3 -0
- package/dist/commands/completion.d.ts.map +1 -0
- package/dist/commands/completion.js +62 -0
- package/dist/commands/completion.js.map +1 -0
- package/dist/commands/context.d.ts +3 -0
- package/dist/commands/context.d.ts.map +1 -0
- package/dist/commands/context.js +94 -0
- package/dist/commands/context.js.map +1 -0
- package/dist/commands/curator.d.ts +14 -0
- package/dist/commands/curator.d.ts.map +1 -1
- package/dist/commands/curator.js +97 -19
- package/dist/commands/curator.js.map +1 -1
- package/dist/commands/customer-needs.d.ts +3 -0
- package/dist/commands/customer-needs.d.ts.map +1 -0
- package/dist/commands/customer-needs.js +198 -0
- package/dist/commands/customer-needs.js.map +1 -0
- package/dist/commands/customers.d.ts +5 -0
- package/dist/commands/customers.d.ts.map +1 -0
- package/dist/commands/customers.js +201 -0
- package/dist/commands/customers.js.map +1 -0
- package/dist/commands/cycles.d.ts +3 -0
- package/dist/commands/cycles.d.ts.map +1 -0
- package/dist/commands/cycles.js +67 -0
- package/dist/commands/cycles.js.map +1 -0
- package/dist/commands/documents.d.ts +3 -0
- package/dist/commands/documents.d.ts.map +1 -0
- package/dist/commands/documents.js +105 -0
- package/dist/commands/documents.js.map +1 -0
- package/dist/commands/favorites.d.ts +3 -0
- package/dist/commands/favorites.d.ts.map +1 -0
- package/dist/commands/favorites.js +101 -0
- package/dist/commands/favorites.js.map +1 -0
- package/dist/commands/index.d.ts +30 -0
- package/dist/commands/index.d.ts.map +1 -1
- package/dist/commands/index.js +30 -0
- package/dist/commands/index.js.map +1 -1
- package/dist/commands/initiatives.d.ts +3 -0
- package/dist/commands/initiatives.d.ts.map +1 -0
- package/dist/commands/initiatives.js +106 -0
- package/dist/commands/initiatives.js.map +1 -0
- package/dist/commands/issues.d.ts +21 -0
- package/dist/commands/issues.d.ts.map +1 -0
- package/dist/commands/issues.js +993 -0
- package/dist/commands/issues.js.map +1 -0
- package/dist/commands/labels.d.ts +3 -0
- package/dist/commands/labels.d.ts.map +1 -0
- package/dist/commands/labels.js +111 -0
- package/dist/commands/labels.js.map +1 -0
- package/dist/commands/milestones.d.ts +3 -0
- package/dist/commands/milestones.d.ts.map +1 -0
- package/dist/commands/milestones.js +94 -0
- package/dist/commands/milestones.js.map +1 -0
- package/dist/commands/notifications.d.ts +3 -0
- package/dist/commands/notifications.d.ts.map +1 -0
- package/dist/commands/notifications.js +130 -0
- package/dist/commands/notifications.js.map +1 -0
- package/dist/commands/project-labels.d.ts +3 -0
- package/dist/commands/project-labels.d.ts.map +1 -0
- package/dist/commands/project-labels.js +80 -0
- package/dist/commands/project-labels.js.map +1 -0
- package/dist/commands/project-relations.d.ts +3 -0
- package/dist/commands/project-relations.d.ts.map +1 -0
- package/dist/commands/project-relations.js +96 -0
- package/dist/commands/project-relations.js.map +1 -0
- package/dist/commands/projects.d.ts +3 -0
- package/dist/commands/projects.d.ts.map +1 -0
- package/dist/commands/projects.js +263 -0
- package/dist/commands/projects.js.map +1 -0
- package/dist/commands/quota.d.ts +3 -0
- package/dist/commands/quota.d.ts.map +1 -0
- package/dist/commands/quota.js +28 -0
- package/dist/commands/quota.js.map +1 -0
- package/dist/commands/reactions.d.ts +7 -0
- package/dist/commands/reactions.d.ts.map +1 -0
- package/dist/commands/reactions.js +53 -0
- package/dist/commands/reactions.js.map +1 -0
- package/dist/commands/relations.d.ts +3 -0
- package/dist/commands/relations.d.ts.map +1 -0
- package/dist/commands/relations.js +73 -0
- package/dist/commands/relations.js.map +1 -0
- package/dist/commands/states.d.ts +3 -0
- package/dist/commands/states.d.ts.map +1 -0
- package/dist/commands/states.js +52 -0
- package/dist/commands/states.js.map +1 -0
- package/dist/commands/status-updates.d.ts +3 -0
- package/dist/commands/status-updates.d.ts.map +1 -0
- package/dist/commands/status-updates.js +117 -0
- package/dist/commands/status-updates.js.map +1 -0
- package/dist/commands/sync.d.ts.map +1 -1
- package/dist/commands/sync.js +58 -18
- package/dist/commands/sync.js.map +1 -1
- package/dist/commands/teams.d.ts +3 -0
- package/dist/commands/teams.d.ts.map +1 -0
- package/dist/commands/teams.js +135 -0
- package/dist/commands/teams.js.map +1 -0
- package/dist/commands/templates.d.ts +3 -0
- package/dist/commands/templates.d.ts.map +1 -0
- package/dist/commands/templates.js +76 -0
- package/dist/commands/templates.js.map +1 -0
- package/dist/commands/users.d.ts +3 -0
- package/dist/commands/users.d.ts.map +1 -0
- package/dist/commands/users.js +40 -0
- package/dist/commands/users.js.map +1 -0
- package/dist/commands/views.d.ts +3 -0
- package/dist/commands/views.d.ts.map +1 -0
- package/dist/commands/views.js +177 -0
- package/dist/commands/views.js.map +1 -0
- package/dist/commands/webhooks.d.ts +3 -0
- package/dist/commands/webhooks.d.ts.map +1 -0
- package/dist/commands/webhooks.js +234 -0
- package/dist/commands/webhooks.js.map +1 -0
- package/dist/config/loader.d.ts.map +1 -1
- package/dist/config/loader.js +3 -0
- package/dist/config/loader.js.map +1 -1
- package/dist/config/types.d.ts +15 -1
- package/dist/config/types.d.ts.map +1 -1
- package/dist/config/types.js +1 -0
- package/dist/config/types.js.map +1 -1
- package/dist/curator/dispatch.d.ts +52 -0
- package/dist/curator/dispatch.d.ts.map +1 -0
- package/dist/curator/dispatch.js +144 -0
- package/dist/curator/dispatch.js.map +1 -0
- package/dist/curator/index.d.ts +5 -0
- package/dist/curator/index.d.ts.map +1 -0
- package/dist/curator/index.js +5 -0
- package/dist/curator/index.js.map +1 -0
- package/dist/curator/llm.d.ts +70 -0
- package/dist/curator/llm.d.ts.map +1 -0
- package/dist/curator/llm.js +107 -0
- package/dist/curator/llm.js.map +1 -0
- package/dist/curator/snapshot.d.ts +34 -0
- package/dist/curator/snapshot.d.ts.map +1 -0
- package/dist/curator/snapshot.js +127 -0
- package/dist/curator/snapshot.js.map +1 -0
- package/dist/curator/state.d.ts +50 -0
- package/dist/curator/state.d.ts.map +1 -0
- package/dist/curator/state.js +125 -0
- package/dist/curator/state.js.map +1 -0
- package/dist/lib/bulk-graphql.d.ts +144 -0
- package/dist/lib/bulk-graphql.d.ts.map +1 -0
- package/dist/lib/bulk-graphql.js +380 -0
- package/dist/lib/bulk-graphql.js.map +1 -0
- package/dist/lib/index.d.ts +2 -0
- package/dist/lib/index.d.ts.map +1 -0
- package/dist/lib/index.js +2 -0
- package/dist/lib/index.js.map +1 -0
- package/dist/output/cli.d.ts +17 -0
- package/dist/output/cli.d.ts.map +1 -0
- package/dist/output/cli.js +252 -0
- package/dist/output/cli.js.map +1 -0
- package/dist/output/formatter.d.ts +6 -0
- package/dist/output/formatter.d.ts.map +1 -1
- package/dist/output/formatter.js +10 -0
- package/dist/output/formatter.js.map +1 -1
- package/dist/output/index.d.ts +1 -0
- package/dist/output/index.d.ts.map +1 -1
- package/dist/output/index.js +1 -0
- package/dist/output/index.js.map +1 -1
- package/dist/scripts/sync-linear-templates.d.ts +26 -0
- package/dist/scripts/sync-linear-templates.d.ts.map +1 -0
- package/dist/scripts/sync-linear-templates.js +115 -0
- package/dist/scripts/sync-linear-templates.js.map +1 -0
- package/dist/signals/github-commits.d.ts +31 -0
- package/dist/signals/github-commits.d.ts.map +1 -0
- package/dist/signals/github-commits.js +127 -0
- package/dist/signals/github-commits.js.map +1 -0
- package/dist/signals/github-pr.d.ts +16 -0
- package/dist/signals/github-pr.d.ts.map +1 -0
- package/dist/signals/github-pr.js +98 -0
- package/dist/signals/github-pr.js.map +1 -0
- package/dist/signals/index.d.ts +4 -0
- package/dist/signals/index.d.ts.map +1 -1
- package/dist/signals/index.js +4 -0
- package/dist/signals/index.js.map +1 -1
- package/dist/signals/linear-issues.d.ts +20 -0
- package/dist/signals/linear-issues.d.ts.map +1 -0
- package/dist/signals/linear-issues.js +115 -0
- package/dist/signals/linear-issues.js.map +1 -0
- package/dist/signals/registry.d.ts +4 -3
- package/dist/signals/registry.d.ts.map +1 -1
- package/dist/signals/registry.js +33 -11
- package/dist/signals/registry.js.map +1 -1
- package/dist/signals/slack-messages.d.ts +20 -0
- package/dist/signals/slack-messages.d.ts.map +1 -0
- package/dist/signals/slack-messages.js +129 -0
- package/dist/signals/slack-messages.js.map +1 -0
- package/dist/utils/errors.d.ts +63 -0
- package/dist/utils/errors.d.ts.map +1 -0
- package/dist/utils/errors.js +94 -0
- package/dist/utils/errors.js.map +1 -0
- package/dist/utils/index.d.ts +9 -0
- package/dist/utils/index.d.ts.map +1 -0
- package/dist/utils/index.js +9 -0
- package/dist/utils/index.js.map +1 -0
- package/dist/utils/label-policy.d.ts +53 -0
- package/dist/utils/label-policy.d.ts.map +1 -0
- package/dist/utils/label-policy.js +93 -0
- package/dist/utils/label-policy.js.map +1 -0
- package/dist/utils/parse.d.ts +48 -0
- package/dist/utils/parse.d.ts.map +1 -0
- package/dist/utils/parse.js +133 -0
- package/dist/utils/parse.js.map +1 -0
- package/dist/utils/project-status.d.ts +6 -0
- package/dist/utils/project-status.d.ts.map +1 -0
- package/dist/utils/project-status.js +33 -0
- package/dist/utils/project-status.js.map +1 -0
- package/dist/utils/rate-limit.d.ts +24 -0
- package/dist/utils/rate-limit.d.ts.map +1 -0
- package/dist/utils/rate-limit.js +89 -0
- package/dist/utils/rate-limit.js.map +1 -0
- package/dist/utils/resolve.d.ts +84 -0
- package/dist/utils/resolve.d.ts.map +1 -0
- package/dist/utils/resolve.js +172 -0
- package/dist/utils/resolve.js.map +1 -0
- package/dist/utils/sleep.d.ts +2 -0
- package/dist/utils/sleep.d.ts.map +1 -0
- package/dist/utils/sleep.js +4 -0
- package/dist/utils/sleep.js.map +1 -0
- package/dist/utils/webhook-verify.d.ts +42 -0
- package/dist/utils/webhook-verify.d.ts.map +1 -0
- package/dist/utils/webhook-verify.js +65 -0
- package/dist/utils/webhook-verify.js.map +1 -0
- package/package.json +4 -1
- package/references/agent-description-template.md +31 -0
- package/references/cli-reference.md +227 -0
- package/references/curator-tiering-rules.md +76 -0
- package/references/label-policy.example.json +37 -0
- package/references/label-policy.placeholder.json +6 -0
- package/references/settings-template.md +30 -0
- package/references/sla-reference.md +70 -0
- package/references/template-index.md +34 -0
- package/references/workspace-labels.md +124 -0
- package/references/workspace-projects.md +56 -0
- package/references/workspace-routing.md +58 -0
- package/schemas/label-policy.json +72 -0
- package/skills/linear-workspace/SKILL.md +65 -4
- package/templates/ACC-PRO-provision.md +74 -0
- package/templates/ACC-PRV-privileged.md +66 -0
- package/templates/ACC-QTR-review.md +77 -0
- package/templates/ACC-REV-revoke.md +67 -0
- package/templates/AI-USE-capability.md +111 -0
- package/templates/AUD-CAP-corrective.md +89 -0
- package/templates/AUD-INT-internal.md +92 -0
- package/templates/AUD-MGT-management.md +110 -0
- package/templates/CHG-MAJ-major.md +110 -0
- package/templates/CHG-SIG-significant.md +83 -0
- package/templates/CHG-STD-standard.md +47 -0
- package/templates/LRN-DOC-lessons.md +75 -0
- package/templates/OPS-BCK-backup.md +99 -0
- package/templates/OPS-DAT-data-mod.md +98 -0
- package/templates/RCA-DOC-root-cause.md +105 -0
- package/templates/RSK-ASS-assessment.md +87 -0
- package/templates/RSK-VND-vendor.md +113 -0
- package/templates/SEC-INC-incident.md +76 -0
- package/templates/SEC-PEN-pentest.md +58 -0
- package/templates/SEC-VLN-vulnerability.md +69 -0
- package/templates/SLA-AVL-availability.md +86 -0
- package/templates/SLA-OPS-operational.md +70 -0
- package/templates/agent-server-template/README.md +88 -0
- package/templates/agent-server-template/server.example.ts +185 -0
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
# AUD-CAP: Corrective Action Plan
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 5-30 days (severity-based)
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Corrective Actions
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: bug`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: [affected area]`
|
|
12
|
+
- Severity: Major NC = High, Minor NC = Medium
|
|
13
|
+
|
|
14
|
+
## Issue Template
|
|
15
|
+
```markdown
|
|
16
|
+
## Corrective Action Plan
|
|
17
|
+
|
|
18
|
+
**CAP ID:** AUD-CAP-YYYY-XXX
|
|
19
|
+
**Source:** [Internal Audit / External Audit / Incident / Management Review]
|
|
20
|
+
**Source Reference:** [Audit report ID or incident ID]
|
|
21
|
+
**Finding Date:** [YYYY-MM-DD]
|
|
22
|
+
|
|
23
|
+
## Finding Details
|
|
24
|
+
- **Finding Type:** [Major NC / Minor NC / Opportunity for Improvement]
|
|
25
|
+
- **Control/Area:** [ISO 27001 control reference or ISMS area]
|
|
26
|
+
- **Finding Description:** [Detailed description of the nonconformity]
|
|
27
|
+
- **Evidence:** [What evidence demonstrated the NC]
|
|
28
|
+
|
|
29
|
+
## Root Cause Analysis
|
|
30
|
+
**Immediate Cause:**
|
|
31
|
+
[What directly caused the NC]
|
|
32
|
+
|
|
33
|
+
**Root Cause:**
|
|
34
|
+
[Underlying reason - use 5 Whys if needed]
|
|
35
|
+
|
|
36
|
+
**Contributing Factors:**
|
|
37
|
+
[Other factors that contributed]
|
|
38
|
+
|
|
39
|
+
## Corrective Action Plan
|
|
40
|
+
|
|
41
|
+
### Immediate Actions (Containment)
|
|
42
|
+
| Action | Owner | Deadline | Status |
|
|
43
|
+
|--------|-------|----------|--------|
|
|
44
|
+
| | | | |
|
|
45
|
+
|
|
46
|
+
### Corrective Actions (Fix Root Cause)
|
|
47
|
+
| Action | Owner | Deadline | Status |
|
|
48
|
+
|--------|-------|----------|--------|
|
|
49
|
+
| | | | |
|
|
50
|
+
|
|
51
|
+
### Preventive Actions (Prevent Recurrence)
|
|
52
|
+
| Action | Owner | Deadline | Status |
|
|
53
|
+
|--------|-------|----------|--------|
|
|
54
|
+
| | | | |
|
|
55
|
+
|
|
56
|
+
## Resource Requirements
|
|
57
|
+
- **Personnel:** [Time/effort needed]
|
|
58
|
+
- **Budget:** [If applicable]
|
|
59
|
+
- **Tools/Systems:** [If needed]
|
|
60
|
+
|
|
61
|
+
## Documentation Updates Required
|
|
62
|
+
- [ ] Policy update needed: [Which policy]
|
|
63
|
+
- [ ] Procedure update needed: [Which procedure]
|
|
64
|
+
- [ ] Training update needed: [Which training]
|
|
65
|
+
- [ ] Risk register update needed
|
|
66
|
+
|
|
67
|
+
## Effectiveness Verification
|
|
68
|
+
**Verification Method:**
|
|
69
|
+
[How will we verify the corrective action was effective?]
|
|
70
|
+
|
|
71
|
+
**Verification Date:**
|
|
72
|
+
[When will effectiveness be checked]
|
|
73
|
+
|
|
74
|
+
**Verification Results:**
|
|
75
|
+
[To be completed after verification]
|
|
76
|
+
|
|
77
|
+
## Approvals
|
|
78
|
+
- [ ] Action plan approved by: _________________ Date: _______
|
|
79
|
+
- [ ] Implementation verified by: _________________ Date: _______
|
|
80
|
+
- [ ] Effectiveness verified by: _________________ Date: _______
|
|
81
|
+
|
|
82
|
+
## Closure
|
|
83
|
+
- [ ] All actions completed
|
|
84
|
+
- [ ] Effectiveness verified
|
|
85
|
+
- [ ] Documentation updated
|
|
86
|
+
- [ ] Finding closed
|
|
87
|
+
|
|
88
|
+
Closure Date: _________________ Closed By: _________________
|
|
89
|
+
```
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# AUD-INT: Internal Audit
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 60 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Internal Audits
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: research`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: [scope-dependent]`
|
|
12
|
+
|
|
13
|
+
## Issue Template
|
|
14
|
+
```markdown
|
|
15
|
+
## ISMS Internal Audit
|
|
16
|
+
|
|
17
|
+
**Audit ID:** AUD-INT-YYYY-XXX
|
|
18
|
+
**Audit Period:** [YYYY-MM-DD to YYYY-MM-DD]
|
|
19
|
+
**Audit Type:** [Annual / Ad-hoc / Follow-up]
|
|
20
|
+
|
|
21
|
+
## Audit Planning
|
|
22
|
+
|
|
23
|
+
### Scope
|
|
24
|
+
[Define audit scope - which ISMS areas, controls, processes]
|
|
25
|
+
|
|
26
|
+
### Objectives
|
|
27
|
+
1. [Objective 1]
|
|
28
|
+
2. [Objective 2]
|
|
29
|
+
3. [Objective 3]
|
|
30
|
+
|
|
31
|
+
### Auditor Information
|
|
32
|
+
- **Lead Auditor:** [Name]
|
|
33
|
+
- **Auditor(s):** [Names]
|
|
34
|
+
- **Independence Verification:** [Confirm auditors not implementing controls being audited]
|
|
35
|
+
|
|
36
|
+
### Audit Schedule
|
|
37
|
+
| Date | Activity | Area/Control | Interviewee |
|
|
38
|
+
|------|----------|--------------|-------------|
|
|
39
|
+
| | | | |
|
|
40
|
+
|
|
41
|
+
## Audit Criteria
|
|
42
|
+
- ISO 27001:2022 requirements
|
|
43
|
+
- Statement of Applicability controls
|
|
44
|
+
- Internal policies and procedures
|
|
45
|
+
- Regulatory requirements
|
|
46
|
+
|
|
47
|
+
## Documents to Review
|
|
48
|
+
- [ ] Information Security Policy
|
|
49
|
+
- [ ] Risk Assessment and Treatment Plan
|
|
50
|
+
- [ ] Statement of Applicability
|
|
51
|
+
- [ ] [Other relevant documents]
|
|
52
|
+
|
|
53
|
+
## Audit Execution Checklist
|
|
54
|
+
- [ ] Opening meeting conducted
|
|
55
|
+
- [ ] Document review completed
|
|
56
|
+
- [ ] Interviews conducted
|
|
57
|
+
- [ ] Evidence collected
|
|
58
|
+
- [ ] Control testing performed
|
|
59
|
+
- [ ] Closing meeting conducted
|
|
60
|
+
|
|
61
|
+
## Findings Summary
|
|
62
|
+
|
|
63
|
+
### Major Nonconformities
|
|
64
|
+
| Finding ID | Control/Area | Description | Evidence |
|
|
65
|
+
|------------|--------------|-------------|----------|
|
|
66
|
+
| | | | |
|
|
67
|
+
|
|
68
|
+
### Minor Nonconformities
|
|
69
|
+
| Finding ID | Control/Area | Description | Evidence |
|
|
70
|
+
|------------|--------------|-------------|----------|
|
|
71
|
+
| | | | |
|
|
72
|
+
|
|
73
|
+
### Opportunities for Improvement
|
|
74
|
+
| OFI ID | Area | Recommendation |
|
|
75
|
+
|--------|------|----------------|
|
|
76
|
+
| | | |
|
|
77
|
+
|
|
78
|
+
### Conforming Controls
|
|
79
|
+
[List controls found to be operating effectively]
|
|
80
|
+
|
|
81
|
+
## Corrective Action Requirements
|
|
82
|
+
[Create linked AUD-CAP tickets for each NC]
|
|
83
|
+
|
|
84
|
+
## Report Distribution
|
|
85
|
+
- [ ] Draft report to Information Security Leader
|
|
86
|
+
- [ ] Final report to ISMS Governance Council
|
|
87
|
+
- [ ] Highlights presented at Management Review
|
|
88
|
+
|
|
89
|
+
## Sign-off
|
|
90
|
+
- [ ] Lead Auditor: _________________ Date: _______
|
|
91
|
+
- [ ] Information Security Leader Review: _________________ Date: _______
|
|
92
|
+
```
|
|
@@ -0,0 +1,110 @@
|
|
|
1
|
+
# AUD-MGT: Management Review
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 30 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Management Reviews
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: research`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: devops`
|
|
12
|
+
|
|
13
|
+
## Issue Template
|
|
14
|
+
```markdown
|
|
15
|
+
## ISMS Management Review
|
|
16
|
+
|
|
17
|
+
**Review ID:** AUD-MGT-YYYY-XXX
|
|
18
|
+
**Review Date:** [YYYY-MM-DD]
|
|
19
|
+
**Review Period:** [Period being reviewed]
|
|
20
|
+
**Meeting Type:** [Annual / Quarterly / Ad-hoc]
|
|
21
|
+
|
|
22
|
+
## Pre-Meeting Preparation
|
|
23
|
+
|
|
24
|
+
### Required Inputs to Compile
|
|
25
|
+
- [ ] Status of previous management review actions
|
|
26
|
+
- [ ] Changes in external/internal context
|
|
27
|
+
- [ ] Changes in interested parties' needs
|
|
28
|
+
- [ ] ISMS performance metrics
|
|
29
|
+
- [ ] Audit results (internal and external)
|
|
30
|
+
- [ ] Nonconformity and corrective action status
|
|
31
|
+
- [ ] Risk assessment status
|
|
32
|
+
- [ ] Incident summary and trends
|
|
33
|
+
- [ ] Security objectives progress
|
|
34
|
+
- [ ] Feedback from stakeholders
|
|
35
|
+
|
|
36
|
+
## Attendees (ISMS Governance Council)
|
|
37
|
+
| Name | Role | Present |
|
|
38
|
+
|------|------|---------|
|
|
39
|
+
| | CEO | [ ] |
|
|
40
|
+
| | CTO | [ ] |
|
|
41
|
+
| | | [ ] |
|
|
42
|
+
|
|
43
|
+
## Agenda
|
|
44
|
+
|
|
45
|
+
### 1. Previous Review Actions Status
|
|
46
|
+
| Action | Owner | Status | Notes |
|
|
47
|
+
|--------|-------|--------|-------|
|
|
48
|
+
| | | | |
|
|
49
|
+
|
|
50
|
+
### 2. Context Changes
|
|
51
|
+
**External Changes:**
|
|
52
|
+
[Changes in regulatory, market, technology landscape]
|
|
53
|
+
|
|
54
|
+
**Internal Changes:**
|
|
55
|
+
[Organizational, process, technology changes]
|
|
56
|
+
|
|
57
|
+
### 3. Performance Review
|
|
58
|
+
**Security Metrics:**
|
|
59
|
+
| Metric | Target | Actual | Status |
|
|
60
|
+
|--------|--------|--------|--------|
|
|
61
|
+
| | | | |
|
|
62
|
+
|
|
63
|
+
**Objectives Progress:**
|
|
64
|
+
| Objective | Progress | Status |
|
|
65
|
+
|-----------|----------|--------|
|
|
66
|
+
| | | |
|
|
67
|
+
|
|
68
|
+
### 4. Audit Results Summary
|
|
69
|
+
- Internal audit findings: [Summary]
|
|
70
|
+
- External audit findings: [Summary]
|
|
71
|
+
- Open nonconformities: [Count and summary]
|
|
72
|
+
|
|
73
|
+
### 5. Risk Assessment Status
|
|
74
|
+
- Risk register status: [Summary]
|
|
75
|
+
- High risks: [List]
|
|
76
|
+
- Risk treatment plan progress: [Summary]
|
|
77
|
+
|
|
78
|
+
### 6. Incident Summary
|
|
79
|
+
- Total incidents this period: [Count]
|
|
80
|
+
- Incidents by severity: [Breakdown]
|
|
81
|
+
- Key incident trends: [Summary]
|
|
82
|
+
- Lessons learned implemented: [Summary]
|
|
83
|
+
|
|
84
|
+
### 7. Resource Requirements
|
|
85
|
+
[Budget, personnel, tool needs]
|
|
86
|
+
|
|
87
|
+
## Decisions Made
|
|
88
|
+
|
|
89
|
+
### ISMS Changes Approved
|
|
90
|
+
| Change | Approved | Owner | Deadline |
|
|
91
|
+
|--------|----------|-------|----------|
|
|
92
|
+
| | Yes/No | | |
|
|
93
|
+
|
|
94
|
+
### Actions Assigned
|
|
95
|
+
| Action | Owner | Deadline | Priority |
|
|
96
|
+
|--------|-------|----------|----------|
|
|
97
|
+
| | | | |
|
|
98
|
+
|
|
99
|
+
### Resource Approvals
|
|
100
|
+
| Request | Approved | Amount | Notes |
|
|
101
|
+
|---------|----------|--------|-------|
|
|
102
|
+
| | Yes/No | | |
|
|
103
|
+
|
|
104
|
+
## Sign-off
|
|
105
|
+
All Governance Council members approve these minutes and decisions:
|
|
106
|
+
|
|
107
|
+
| Name | Signature | Date |
|
|
108
|
+
|------|-----------|------|
|
|
109
|
+
| | | |
|
|
110
|
+
```
|
|
@@ -0,0 +1,110 @@
|
|
|
1
|
+
# CHG-MAJ: ISMS Major Change (Category 3)
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 15-30 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Major Changes
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: feature` or `Type: improvement`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Flag: security`
|
|
12
|
+
- `Layer: [all affected layers]`
|
|
13
|
+
|
|
14
|
+
## Issue Template
|
|
15
|
+
```markdown
|
|
16
|
+
## ISMS Major Change Request
|
|
17
|
+
|
|
18
|
+
**Change ID:** ISMS-YYYY-XXX
|
|
19
|
+
**Category:** 3 - Major Change
|
|
20
|
+
**Requested By:** [Name]
|
|
21
|
+
**Date Requested:** [YYYY-MM-DD]
|
|
22
|
+
**Target Implementation:** [YYYY-MM-DD] (minimum 30 days from request)
|
|
23
|
+
|
|
24
|
+
## Change Description
|
|
25
|
+
[Comprehensive description - affects ISMS scope/boundaries, security policy intent, organizational structure, introduces new technology, responds to regulatory changes, or post-incident modifications]
|
|
26
|
+
|
|
27
|
+
## Change Type
|
|
28
|
+
- [ ] ISMS scope or boundary change
|
|
29
|
+
- [ ] Security policy intent change
|
|
30
|
+
- [ ] Organizational structure change
|
|
31
|
+
- [ ] New technology introduction
|
|
32
|
+
- [ ] Regulatory/legal requirement change
|
|
33
|
+
- [ ] Post-incident modification
|
|
34
|
+
- [ ] Other: ___
|
|
35
|
+
|
|
36
|
+
## Affected Areas
|
|
37
|
+
### Documents
|
|
38
|
+
| Document | Section | Type of Change |
|
|
39
|
+
|----------|---------|----------------|
|
|
40
|
+
| | | |
|
|
41
|
+
|
|
42
|
+
### Systems
|
|
43
|
+
[List all affected systems]
|
|
44
|
+
|
|
45
|
+
### Processes
|
|
46
|
+
[List all affected business processes]
|
|
47
|
+
|
|
48
|
+
### Personnel/Roles
|
|
49
|
+
[List affected roles and responsibilities]
|
|
50
|
+
|
|
51
|
+
## Business Justification
|
|
52
|
+
[Detailed justification including strategic alignment]
|
|
53
|
+
|
|
54
|
+
## Comprehensive Risk Assessment
|
|
55
|
+
### Identified Risks
|
|
56
|
+
| Risk | Likelihood | Impact | Risk Level | Mitigation |
|
|
57
|
+
|------|------------|--------|------------|------------|
|
|
58
|
+
| | | | | |
|
|
59
|
+
|
|
60
|
+
### Risk Treatment Decisions
|
|
61
|
+
[Document risk treatment approach for each identified risk]
|
|
62
|
+
|
|
63
|
+
## Resource Requirements
|
|
64
|
+
- **Personnel:** [Detailed time/effort breakdown]
|
|
65
|
+
- **Budget:** [Cost estimate with breakdown]
|
|
66
|
+
- **Training:** [Training plan if required]
|
|
67
|
+
- **External Support:** [Consultants/vendors if needed]
|
|
68
|
+
|
|
69
|
+
## Implementation Plan
|
|
70
|
+
| Phase | Milestone | Actions | Owner | Start | End |
|
|
71
|
+
|-------|-----------|---------|-------|-------|-----|
|
|
72
|
+
| 1 | | | | | |
|
|
73
|
+
| 2 | | | | | |
|
|
74
|
+
|
|
75
|
+
## Rollback Plan
|
|
76
|
+
[Comprehensive rollback procedure]
|
|
77
|
+
|
|
78
|
+
## Communication Plan
|
|
79
|
+
| Audience | Message | Channel | Timing |
|
|
80
|
+
|----------|---------|---------|--------|
|
|
81
|
+
| | | | |
|
|
82
|
+
|
|
83
|
+
## Training Plan
|
|
84
|
+
[If applicable - training requirements and schedule]
|
|
85
|
+
|
|
86
|
+
## Approvals (Full ISMS Governance Council)
|
|
87
|
+
Management Review Meeting Date: [YYYY-MM-DD]
|
|
88
|
+
|
|
89
|
+
| Council Member | Role | Signature | Date |
|
|
90
|
+
|----------------|------|-----------|------|
|
|
91
|
+
| | CEO | | |
|
|
92
|
+
| | CTO | | |
|
|
93
|
+
|
|
94
|
+
## Implementation Tracking
|
|
95
|
+
- [ ] 30-day notice period completed
|
|
96
|
+
- [ ] All approvals obtained
|
|
97
|
+
- [ ] Implementation commenced
|
|
98
|
+
- [ ] Milestone 1 complete
|
|
99
|
+
- [ ] Milestone 2 complete
|
|
100
|
+
- [ ] Full implementation complete
|
|
101
|
+
- [ ] Post-implementation review scheduled
|
|
102
|
+
|
|
103
|
+
## Verification Checklist
|
|
104
|
+
- [ ] Change implemented per plan
|
|
105
|
+
- [ ] All affected documents updated
|
|
106
|
+
- [ ] Training completed (if required)
|
|
107
|
+
- [ ] Change log updated
|
|
108
|
+
- [ ] Effectiveness review scheduled
|
|
109
|
+
- [ ] Lessons learned documented
|
|
110
|
+
```
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
# CHG-SIG: ISMS Significant Change (Category 2)
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 5-10 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Significant Changes
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: improvement`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Flag: security` (if security control affected)
|
|
12
|
+
- `Layer: [affected layers]`
|
|
13
|
+
|
|
14
|
+
## Issue Template
|
|
15
|
+
```markdown
|
|
16
|
+
## ISMS Significant Change Request
|
|
17
|
+
|
|
18
|
+
**Change ID:** ISMS-YYYY-XXX
|
|
19
|
+
**Category:** 2 - Significant Change
|
|
20
|
+
**Requested By:** [Name]
|
|
21
|
+
**Date Requested:** [YYYY-MM-DD]
|
|
22
|
+
**Target Implementation:** [YYYY-MM-DD]
|
|
23
|
+
|
|
24
|
+
## Change Description
|
|
25
|
+
[Detailed description - affects existing security controls, procedures, risk treatment plans, or objectives]
|
|
26
|
+
|
|
27
|
+
## Affected Areas
|
|
28
|
+
- [ ] Security controls
|
|
29
|
+
- [ ] Procedures
|
|
30
|
+
- [ ] Risk treatment plans
|
|
31
|
+
- [ ] ISMS objectives
|
|
32
|
+
- [ ] Other: ___
|
|
33
|
+
|
|
34
|
+
## Affected Documents
|
|
35
|
+
| Document | Section | Type of Change |
|
|
36
|
+
|----------|---------|----------------|
|
|
37
|
+
| | | |
|
|
38
|
+
|
|
39
|
+
## Justification
|
|
40
|
+
[Business or security justification for this change]
|
|
41
|
+
|
|
42
|
+
## Impact Assessment
|
|
43
|
+
### Systems Affected
|
|
44
|
+
[List systems or processes affected]
|
|
45
|
+
|
|
46
|
+
### Stakeholders Affected
|
|
47
|
+
[List roles or teams impacted]
|
|
48
|
+
|
|
49
|
+
### Potential Risks
|
|
50
|
+
[Describe potential negative impacts]
|
|
51
|
+
|
|
52
|
+
### Mitigation Measures
|
|
53
|
+
[How will risks be mitigated?]
|
|
54
|
+
|
|
55
|
+
## Resource Requirements
|
|
56
|
+
- **Personnel:** [Time/effort needed]
|
|
57
|
+
- **Budget:** [If applicable]
|
|
58
|
+
- **Training:** [If required]
|
|
59
|
+
|
|
60
|
+
## Implementation Plan
|
|
61
|
+
| Step | Action | Owner | Target Date |
|
|
62
|
+
|------|--------|-------|-------------|
|
|
63
|
+
| 1 | | | |
|
|
64
|
+
| 2 | | | |
|
|
65
|
+
|
|
66
|
+
## Rollback Plan
|
|
67
|
+
[Describe how to revert if change causes issues]
|
|
68
|
+
|
|
69
|
+
## Communication Requirements
|
|
70
|
+
- [ ] Affected stakeholders notified
|
|
71
|
+
- [ ] Training scheduled (if needed)
|
|
72
|
+
|
|
73
|
+
## Approvals
|
|
74
|
+
- [ ] Information Security Management Leader: _________________ Date: _______
|
|
75
|
+
- [ ] ISMS Governance Council Member: _________________ Date: _______
|
|
76
|
+
|
|
77
|
+
## Implementation Verification
|
|
78
|
+
- [ ] Change implemented as planned
|
|
79
|
+
- [ ] No deviations from plan (or deviations documented)
|
|
80
|
+
- [ ] Affected documents updated
|
|
81
|
+
- [ ] Change log updated
|
|
82
|
+
- [ ] Post-implementation review completed
|
|
83
|
+
```
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
# CHG-STD: ISMS Standard Change (Category 1)
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 1-2 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Standard Changes
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: improvement`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: [affected layer]`
|
|
12
|
+
|
|
13
|
+
## Issue Template
|
|
14
|
+
```markdown
|
|
15
|
+
## ISMS Standard Change Request
|
|
16
|
+
|
|
17
|
+
**Change ID:** ISMS-YYYY-XXX
|
|
18
|
+
**Category:** 1 - Standard Change
|
|
19
|
+
**Requested By:** [Name]
|
|
20
|
+
**Date Requested:** [YYYY-MM-DD]
|
|
21
|
+
|
|
22
|
+
## Change Description
|
|
23
|
+
[Describe the change - should be minor documentation updates, clarifications, or non-intent-changing reviews]
|
|
24
|
+
|
|
25
|
+
## Affected Documents
|
|
26
|
+
- [ ] Document: [filename] - Section: [section]
|
|
27
|
+
|
|
28
|
+
## Justification
|
|
29
|
+
[Why is this change needed?]
|
|
30
|
+
|
|
31
|
+
## Risk Assessment
|
|
32
|
+
**Risk Level:** Minimal
|
|
33
|
+
[Standard changes by definition have minimal risk - no changes to security controls or policy intent]
|
|
34
|
+
|
|
35
|
+
## Implementation Plan
|
|
36
|
+
1. [Step 1]
|
|
37
|
+
2. [Step 2]
|
|
38
|
+
|
|
39
|
+
## Approval
|
|
40
|
+
- [ ] Information Security Management Leader: _________________ Date: _______
|
|
41
|
+
|
|
42
|
+
## Verification Checklist
|
|
43
|
+
- [ ] Change implemented as described
|
|
44
|
+
- [ ] Document version updated
|
|
45
|
+
- [ ] Change log updated
|
|
46
|
+
- [ ] No unintended impacts observed
|
|
47
|
+
```
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
# LRN-DOC: Lessons Learned
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** 10-20 days
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Lessons Learned
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: research`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: [affected area]`
|
|
12
|
+
|
|
13
|
+
## Issue Template
|
|
14
|
+
```markdown
|
|
15
|
+
## Lessons Learned Review
|
|
16
|
+
|
|
17
|
+
**Review ID:** LRN-YYYY-XXX
|
|
18
|
+
**Incident Reference:** [Link to incident ticket]
|
|
19
|
+
**RCA Reference:** [Link to RCA ticket]
|
|
20
|
+
**Meeting Date:** [YYYY-MM-DD]
|
|
21
|
+
|
|
22
|
+
## Meeting Details
|
|
23
|
+
- **Facilitator:** [Name]
|
|
24
|
+
- **Participants:** [List all participants]
|
|
25
|
+
- **Duration:** [X hours]
|
|
26
|
+
|
|
27
|
+
## Incident Recap
|
|
28
|
+
[Brief summary of the incident - link to full RCA for details]
|
|
29
|
+
|
|
30
|
+
## Discussion Topics
|
|
31
|
+
|
|
32
|
+
### What Went Well
|
|
33
|
+
| Item | Details | How to Reinforce |
|
|
34
|
+
|------|---------|------------------|
|
|
35
|
+
| | | |
|
|
36
|
+
|
|
37
|
+
### What Could Be Improved
|
|
38
|
+
| Item | Details | Proposed Improvement |
|
|
39
|
+
|------|---------|---------------------|
|
|
40
|
+
| | | |
|
|
41
|
+
|
|
42
|
+
### What Was Confusing or Unclear
|
|
43
|
+
| Item | Details | Clarification Needed |
|
|
44
|
+
|------|---------|---------------------|
|
|
45
|
+
| | | |
|
|
46
|
+
|
|
47
|
+
## Key Learnings
|
|
48
|
+
1. [Learning 1]
|
|
49
|
+
2. [Learning 2]
|
|
50
|
+
3. [Learning 3]
|
|
51
|
+
|
|
52
|
+
## Action Items
|
|
53
|
+
| Action | Owner | Target Date | Priority | Ticket |
|
|
54
|
+
|--------|-------|-------------|----------|--------|
|
|
55
|
+
| | | | | |
|
|
56
|
+
|
|
57
|
+
## Process Improvements
|
|
58
|
+
[Suggested changes to incident response or other processes]
|
|
59
|
+
|
|
60
|
+
## Training Needs
|
|
61
|
+
[Any training identified as needed]
|
|
62
|
+
|
|
63
|
+
## Documentation Updates
|
|
64
|
+
- [ ] Runbook updates needed
|
|
65
|
+
- [ ] Procedure updates needed
|
|
66
|
+
- [ ] Training material updates needed
|
|
67
|
+
|
|
68
|
+
## Follow-up
|
|
69
|
+
- [ ] Action items created in Linear
|
|
70
|
+
- [ ] Next check-in date: [YYYY-MM-DD]
|
|
71
|
+
|
|
72
|
+
## Sign-off
|
|
73
|
+
- [ ] Facilitator: _________________ Date: _______
|
|
74
|
+
- [ ] Team Lead: _________________ Date: _______
|
|
75
|
+
```
|
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# OPS-BCK: Backup Restore Test
|
|
2
|
+
|
|
3
|
+
## Quick Reference
|
|
4
|
+
- **SLA:** RTO: 2 hours
|
|
5
|
+
- **Team:** *the team that owns this workflow in your workspace*
|
|
6
|
+
- **Project:** Backup & DR Testing
|
|
7
|
+
|
|
8
|
+
## Required Labels
|
|
9
|
+
- `Type: research`
|
|
10
|
+
- `Flag: compliance`
|
|
11
|
+
- `Layer: devops`
|
|
12
|
+
|
|
13
|
+
## Issue Template
|
|
14
|
+
```markdown
|
|
15
|
+
## Backup Restore Test
|
|
16
|
+
|
|
17
|
+
**Test ID:** OPS-BCK-YYYY-QX
|
|
18
|
+
**Test Date:** [YYYY-MM-DD]
|
|
19
|
+
**Quarter:** Q[1-4] [YYYY]
|
|
20
|
+
**Test Type:** [RDS Snapshot / RDS Point-in-Time / S3 Version / Full DR Simulation]
|
|
21
|
+
|
|
22
|
+
## Recovery Objectives
|
|
23
|
+
- **RTO (Recovery Time Objective):** 2 hours
|
|
24
|
+
- **RPO (Recovery Point Objective):** 15 minutes
|
|
25
|
+
|
|
26
|
+
## Test Scope
|
|
27
|
+
- [ ] RDS PostgreSQL Database
|
|
28
|
+
- [ ] S3 Production Bucket
|
|
29
|
+
- [ ] ECR Container Images (Q4 only)
|
|
30
|
+
- [ ] ECS Task Definitions (Q4 only)
|
|
31
|
+
|
|
32
|
+
## Pre-Test Checklist
|
|
33
|
+
- [ ] Test environment prepared
|
|
34
|
+
- [ ] Backup source identified (snapshot ID or timestamp)
|
|
35
|
+
- [ ] Test plan reviewed
|
|
36
|
+
- [ ] Rollback plan ready
|
|
37
|
+
|
|
38
|
+
## Test Execution
|
|
39
|
+
|
|
40
|
+
### Test 1: [Test Type]
|
|
41
|
+
**Start Time:** [HH:MM]
|
|
42
|
+
**End Time:** [HH:MM]
|
|
43
|
+
**Recovery Time:** [XX minutes]
|
|
44
|
+
|
|
45
|
+
**Steps Performed:**
|
|
46
|
+
1. [ ] [Step 1]
|
|
47
|
+
2. [ ] [Step 2]
|
|
48
|
+
3. [ ] [Step 3]
|
|
49
|
+
|
|
50
|
+
**Validation Queries:**
|
|
51
|
+
```sql
|
|
52
|
+
-- Record counts
|
|
53
|
+
SELECT COUNT(*) FROM [table];
|
|
54
|
+
|
|
55
|
+
-- Recent data check
|
|
56
|
+
SELECT * FROM [table] WHERE created_at > NOW() - INTERVAL '7 days' LIMIT 5;
|
|
57
|
+
|
|
58
|
+
-- Data integrity
|
|
59
|
+
[Specific integrity checks]
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
**Results:**
|
|
63
|
+
| Check | Expected | Actual | Pass/Fail |
|
|
64
|
+
|-------|----------|--------|-----------|
|
|
65
|
+
| Recovery time | < 2 hours | | |
|
|
66
|
+
| Data present | Yes | | |
|
|
67
|
+
| No data loss beyond RPO | < 15 min | | |
|
|
68
|
+
| Integrity checks | Pass | | |
|
|
69
|
+
|
|
70
|
+
## Cleanup
|
|
71
|
+
- [ ] Test instances terminated
|
|
72
|
+
- [ ] Test data removed
|
|
73
|
+
- [ ] Costs verified
|
|
74
|
+
|
|
75
|
+
## Issues Encountered
|
|
76
|
+
| Issue | Impact | Resolution | Follow-up Needed |
|
|
77
|
+
|-------|--------|------------|------------------|
|
|
78
|
+
| | | | |
|
|
79
|
+
|
|
80
|
+
## Results Summary
|
|
81
|
+
- **Overall Result:** [PASS / FAIL]
|
|
82
|
+
- **Recovery Time Achieved:** [XX minutes]
|
|
83
|
+
- **Data Loss:** [None / XX minutes]
|
|
84
|
+
- **RTO Met:** [Yes / No]
|
|
85
|
+
- **RPO Met:** [Yes / No]
|
|
86
|
+
|
|
87
|
+
## Corrective Actions
|
|
88
|
+
[Create linked tickets if any issues found]
|
|
89
|
+
|
|
90
|
+
## Sign-off
|
|
91
|
+
- [ ] Test performed by: _________________ Date: _______
|
|
92
|
+
- [ ] Results verified by: _________________ Date: _______
|
|
93
|
+
- [ ] CTO approval: _________________ Date: _______
|
|
94
|
+
|
|
95
|
+
## Evidence
|
|
96
|
+
- [ ] Screenshots captured
|
|
97
|
+
- [ ] Logs preserved
|
|
98
|
+
- [ ] Notion Restore Test Record updated
|
|
99
|
+
```
|