-
|
Hi, just started with App Control and tried using the Application Control 'built-in controls' policy settings.
On the endpoint I installed this great app to monitor what happens but it seems like AppControl Manager doesnt like the Microsoft provided Policies(?). System information -> Retrieve Policies; I see the policy is downloaded and stored in C:\Windows\System32\CodeIntegrity\CIPolicies\Active{e0abda1f-ccf0-468e-8855-3e0f08b02d6a}.CIP but I can't open this policy with the Editor. {e0abda1f-ccf0-468e-8855-3e0f08b02d6a}.zip https://github.com/Harvester57/Code-Integrity-example-policies-Insider/blob/main/DefaultWindows_Audit.xml |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Hi, The CIP file you shared is helpful though, thank you! I just warped up v2.0.62.0: #1024, so i'll add the necessary logic to the update after this, v2.0.63.0 |
Beta Was this translation helpful? Give feedback.
-
|
Hi again, thanks for taking the time to look into this subject. Preliminary findings:
I attached another CIP file coming from the built-in controls with all 3 options enabled, same GUID as the previous one. So decoding this Microsoft built-in controls CIP would help in understanding whats happening, again thanks for the support. Not entitled to anything but instead graceful for all the time developers take to help out the community who benefit eventually of their time and input. |
Beta Was this translation helpful? Give feedback.

Hi,
They are not the same policy, if they were you wouldn't be getting that error. What you're trying to do is reversing a CIP binary file deployed by Microsoft back to XML. Microsoft must be using additional items in the policy they deploy. I will have to add the necessary logic to decode them as well.
The CIP file you shared is helpful though, thank you!
I just warped up v2.0.62.0: #1024, so i'll add the necessary logic to the update after this, v2.0.63.0