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
We've been trying to use the advanced hunting log to create a policy for an application. However, some binaries that are being caught by CI as not meeting enterprise signing requirements as a 3033 event (AppControlCodeIntegrityOriginBlocked) but without an associated 3077 event. As a result they're not getting included in the KQL results.
Just wondering if anyone knows why this might be, and how to capture the details for policy creation centrally (we can remote-admin the machine in question, so can just scan manually for now).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We've been trying to use the advanced hunting log to create a policy for an application. However, some binaries that are being caught by CI as not meeting enterprise signing requirements as a 3033 event (AppControlCodeIntegrityOriginBlocked) but without an associated 3077 event. As a result they're not getting included in the KQL results.
Just wondering if anyone knows why this might be, and how to capture the details for policy creation centrally (we can remote-admin the machine in question, so can just scan manually for now).
Many thanks,
Iain
Beta Was this translation helpful? Give feedback.
All reactions