Conversation
Scopes the control to the audit/compliance evidence SDLC controls produce (review outcomes, test evidence, approvals, build artefacts, audit logs) rather than general enterprise data retention. Requirements trimmed from 10 to 6 bullets; disposal mechanics (sanitisation, legal holds, disposal logging) are deferred to the organisation's general data retention policy instead of being re-specified here. Signed-off-by: Germán Fuentes Capella <47056480+germanptr@users.noreply.github.com>
germanptr
requested review from
aaronsearle,
meekrosoft and
tobyweston
as code owners
September 14, 2026 12:43
germanptr
commented
Sep 14, 2026
| * The organisation MUST classify SDLC-generated governance record and artefact types (such as review outcomes, test evidence, scan results, approval records, deployment records, build artefacts, audit logs, and exception records) and assign each class a minimum retention period | ||
| * The minimum retention period for a record class MUST NOT be less than the longest applicable regulatory, contractual, or audit cycle requirement for that class | ||
| * Records MUST be immutable and tamper-evident for the duration of their minimum retention period; they MUST NOT be modifiable, deletable, or replaceable outside an approved and auditable exception process | ||
| * Retention MUST extend to SDLC records held in third-party or SaaS tooling (such as CI/CD, ticketing, code review, and artefact repositories), through contractual terms, configuration, or export before offboarding |
Contributor
Author
There was a problem hiding this comment.
in accordance to requirement 1
…ent 1 Clarify that the third-party/SaaS retention requirement covers the record classes and minimum periods already established by the classification requirement, rather than reading as a separate, unscoped obligation. Signed-off-by: Germán Fuentes Capella <47056480+germanptr@users.noreply.github.com>
germanptr
force-pushed
the
narrow-mi-22-to-sdlc-scope
branch
from
September 14, 2026 14:29
eba743b to
c775575
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scopes the control to the audit/compliance evidence SDLC controls produce (review outcomes, test evidence, approvals, build artefacts, audit logs) rather than general enterprise data retention.
Requirements trimmed from 10 to 6 bullets; disposal mechanics (sanitisation, legal holds, disposal logging) are deferred to the organisation's general data retention policy instead of being re-specified here.