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

AIP-147: No rules to enforce "sensitive fields" guidance #1429

Open
loeffel-io opened this issue Sep 10, 2024 · 2 comments
Open

AIP-147: No rules to enforce "sensitive fields" guidance #1429

loeffel-io opened this issue Sep 10, 2024 · 2 comments

Comments

@loeffel-io
Copy link
Contributor

It looks like there are no rules for AIP 147 (INPUT_ONLY)

@noahdietz
Copy link
Collaborator

Indeed there are not. I think this is at least partially due to the lack of a strong heuristic/signal to use in identifying the fields that the guidance would pertain to. For example, going off of field name having _secret doesn't really give a strong signal that the field in question is actually sensitive and needs to be handled as AIP-147 describes.

Do you have any suggestions?

I think this might be one of the "suggested pattern" AIPs rather than "required design" AIPs e.g. AIP-131.

@noahdietz noahdietz changed the title AIP 147 AIP-147: No rules to enforce "sensitive fields" guidance Sep 23, 2024
@noahdietz
Copy link
Collaborator

If we had an annotation that identified the contents as a known sensitive data type e.g. a PEM key or that the field's contents were simply "sensitive", we'd be able to definitively identify fields that the guidance applied to.

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

No branches or pull requests

2 participants