Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create ability to ignore default PII scanning patterns #487

Open
JordoHeffernan opened this issue Mar 21, 2024 · 1 comment
Open

Create ability to ignore default PII scanning patterns #487

JordoHeffernan opened this issue Mar 21, 2024 · 1 comment

Comments

@JordoHeffernan
Copy link
Contributor

JordoHeffernan commented Mar 21, 2024

As a user, I want to be able to stop secureli from scanning for the default PII patterns

AC

  1. Add item to .secureli.yaml called ignore-pii-patterns
  2. ignore-pii-patterns can only accept 'email', 'ssn', 'phone'
  3. if one of these items is included in the secureli congif, ignore that category when the PII scan runs
    a. if there are any items in ignore-pii-patterns beyond the acceptable list, throw an error.
  4. add ability to put new items into config via cli, either with a new flag on an existing command or a new command
    a. confirm user's input fits acceptable items, throw an error if it does not
  5. Add note in documentation to notify users of functionality
@JordoHeffernan JordoHeffernan changed the title Add ability to remove default PII scanning categories Add ability to iugnore default PII scanning categories Mar 22, 2024
@JordoHeffernan JordoHeffernan changed the title Add ability to iugnore default PII scanning categories Add ability to ignore default PII scanning categories Mar 22, 2024
@JordoHeffernan JordoHeffernan changed the title Add ability to ignore default PII scanning categories Create ability to ignore default PII scanning categories Mar 22, 2024
@blonienc blonienc changed the title Create ability to ignore default PII scanning categories Create ability to ignore default PII scanning patterns Mar 22, 2024
@blonienc
Copy link

blonienc commented Jun 4, 2024

This was completed in #558.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Discussion Required
Development

No branches or pull requests

2 participants