π‘οΈ Add breach assessment procedures - #10
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
Member
Author
|
Honestly, this and the next PRs might repeat stuff, but that is a design choice. As these procedures expand, they will need the sections (which is why we scoped out #37). So I may say something like "observe the physical attack" multiple times, but in the future, different instances of that phrase in different parts of the docs could mean different things and require different responses based on whether it's the assessment, prevention, or response from backup. |
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
JFWooten4
marked this pull request as ready for review
June 2, 2026 15:30
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
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.
Creates assessment procedures for Regulation S-P incident response under 17 CFR Β§ 248.30, Subsection (a)(3)(i). The procedures should define how BlockTransfer assesses the nature and scope of unauthorized access to or use of customer information, identifies affected customer information systems, determines the types of customer information involved, and supports customer-notification decisions under 17 CFR Β§ 248.30, Subsection (a)(4).
Recordkeeping implementation is out of scope for this PR and should be handled separately under the transfer-agent recordkeeping issue.
Regulatory basis
17 CFR Β§ 248.30, Subsection (a)(3): response program
17 CFR Β§ 248.30, Subsection (a)(3)(i): assessment procedures
17 CFR Β§ 248.30, Subsection (a)(4)(i): notification obligation
17 CFR Β§ 248.30, Subsection (a)(4)(ii): affected individuals
17 CFR Β§ 248.30, Subsection (d)(6): customer information systems
17 CFR Β§ 248.30, Subsection (d)(9): sensitive customer information
Changes to be made