-
Notifications
You must be signed in to change notification settings - Fork 7
[docs] feat(scv): add domains documentation (#236) #237
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
base: main
Are you sure you want to change the base?
Conversation
docs/deployment/breaking-changes.md
Outdated
|
|
||
|
|
||
| <a id="openaev-scv"></a> | ||
| #### OpenAEV SCV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have to do a "OpenAEV 2.1.0" migration section before creating a new migration
| @@ -0,0 +1,22 @@ | |||
| # OpenAEV SCV | |||
|
|
|||
| !!! info "" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry but not sure to understand this "breaking-change". It's not normal to deploy again our Docker when we have our OpenAEV updated ? I thought if OpenAEV is upgraded, all the projects linked are too.
| |------------------------|--------------------------------------------------------------------------------------------------------------------| | ||
| | **ENDPOINT** | Evaluates endpoints security controls such as EDR, SIEM | | ||
| | **DATA EXFILTRATION** | Assesses the ability to detect or block attempts to exfiltrate data and check security controls like DLP & SIEM | | ||
| | **URL FILTERING** | Validates mechanisms controlling web access and URL categorization or filtering with security systems like proxy, ZTNA | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two spaces between filtering and with ;)
| Domains are primarily defined at the Payload level. Each payload declares one or more Domains that describe the security control category involved in its execution. This ensures consistent and predictable classification across the platform. | ||
|
|
||
| ### Injector Contracts | ||
| In some cases, an Injector Contract may also carry a Domain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is is important to describe which cases or not ?
No description provided.