You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most class detail pages are showing the Container profile when the profile is not, in fact, applicable. With the main ocsf-schema, 62 out of 64 classes include the container profile with only base_event and incident_finding not included. The Container profile associated with no classes (per its profile detail page) and is the only profile that is associated with objects.
What might be happening is that class detail "profiles" section is including classes that reference the objects that in turn use the profile, whereas the profile details page is only showing the direct references in the class and object definitions.
The text was updated successfully, but these errors were encountered:
Yep, the container profile applies to process object and most of the classes have process object, thus causing the observed behavior.
rmouritzen-splunk
changed the title
Container profile incorrectly on most class detail pages
Container profile is incorrectly on most class detail pages
Feb 22, 2024
rmouritzen-splunk
changed the title
Container profile is incorrectly on most class detail pages
Container profile is incorrectly shown on most class detail pages
Jun 18, 2024
Most class detail pages are showing the Container profile when the profile is not, in fact, applicable. With the main
ocsf-schema
, 62 out of 64 classes include the container profile with onlybase_event
andincident_finding
not included. The Container profile associated with no classes (per its profile detail page) and is the only profile that is associated with objects.What might be happening is that class detail "profiles" section is including classes that reference the objects that in turn use the profile, whereas the profile details page is only showing the direct references in the class and object definitions.
The text was updated successfully, but these errors were encountered: