🛡️ Add incident response program - #9
Merged
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
JFWooten4
marked this pull request as draft
May 18, 2026 17:46
Member
Author
|
There are bits of this that are written without full contextualization or independent implementation for the sake of (i) time and (ii) merge order. It is not generally possible to cross-reference the other policies that haven't been written yet in the other PRs. |
JFWooten4
marked this pull request as ready for review
June 1, 2026 23:51
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.
Adds a written incident response program for Regulation S-P compliance under 17 CFR § 248.30(a)(3). The program should define how BlockTransfer detects, assesses, contains, controls, recovers from, and escalates unauthorized access to or use of customer information, including when customer notification procedures must be triggered.
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(a)(3): response program
17 CFR § 248.30(a)(4)(i): notification obligation
17 CFR § 248.30(a)(4)(iii): notice timing
17 CFR § 248.30(a)(5): service providers
Changes to be made