-
Notifications
You must be signed in to change notification settings - Fork 137
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
Move 'Network File Activity' and 'Email' classes to 'Application' category #905
Comments
I don't recall us ever deprecating a class before. I am testing from my end, but it is possible that we might need to build a way to introduce class deprecation. UPDATE: this class was deprecated: https://schema.ocsf.io/1.1.0-dev/classes/security_finding?extensions= We should look into a way to denote deprecation on the class view page of the web ui (superscript, maybe?) |
Per today's network call, we discussed the name of We are most likely landing on |
Some other options are:
|
I would stray from Let's keep |
Vote created here: #909 Please cast your vote! |
Completed via #917 |
|
PR is in to move the Email File/URL classes. Once this is merged this Issue can be closed. |
In 1.1 preparation, we determined that Email File and URL classes need some work, and that should precede moving them to the Created new issue #927 to track the 1.2 efforts. |
Network File Activity and Email Activity are much more based on the Application layer. The focal point of those logs are not the network transaction, but what the overarching applications are actually doing.
We are proposing to move these classes under the 'Application' category, which they are more appropriately suited.
Note: Doing so in a non-breaking manner will require class deprecation.
The text was updated successfully, but these errors were encountered: