Addresses issue 19304; needs validation #19677
Open
Conversation
This file contains 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.
Addresses #19304
@swidup before we increase volume, I want to make sure we're doing things correctly so there's only one record here.
I'd prefer to eventually just submit our issues already coded as json so that no one has to code them up. I understand this could cause issues with assignment and duplication, but let me know what works best for you and we'll do our best to make it happen.
Depending on the regulator, we sometimes only have a handful of fields such as company name, number of citizens impacted and date of breach. It varies widely by organization (ex. OCC federal vs Maine OAG). If you'd prefer we only import those regulators where there are plentiful fields, we can do that as well.