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

Framework Advice/Gaps for Cloud Native Asset Types #472

Open
WB-Sh opened this issue Jun 27, 2023 · 0 comments
Open

Framework Advice/Gaps for Cloud Native Asset Types #472

WB-Sh opened this issue Jun 27, 2023 · 0 comments

Comments

@WB-Sh
Copy link

WB-Sh commented Jun 27, 2023

Looking for some advice on the most correct way to describe incidents involving cloud native asset types. Am newer to the VERIS Framework and have been looking on how to describe common incident types that are seen. Examples include cloud native storage (S3/Azure Storage), Kubernetes/Containers, Native WebApps/SQL, Functions/Logics Apps, etc.

Given the example scenario:
An S3 Bucket containing PII has been accidentally left in a publicly accessible mode leading to an actor exfiltrating the data contained therein and making ransom demands to not release the data.

Actor: External - Organized Crime - Financial
Action: Error - Publishing Error - Carelessness
Asset: Server - File - External Hosted - Victim Owned????
Attribute: Confidentiality/Possession - Data Disclosure - Personal Variety

I can force some of these cloud native terms into the Asset Enumerations but then it fails to highlight issues with Cloud Native configurations/incidents when they occur.

I see the Cloud Specific section of the Enum but it's still missing (in my opinion) some of the depth I'm looking for here:
image

Looking for best practices/advice on how to handle this one and if there's some element missing in the framework.

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

No branches or pull requests

1 participant