Skip to content
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

The Unsigned policy rule option is valid for Supplemental types #11898

Merged
merged 1 commit into from
May 20, 2024

Conversation

HotCakeX
Copy link
Contributor

Description

The rule option 6 Enabled:Unsigned System Integrity Policy (Default) is valid for supplemental policies, but the document says no.

Why

In fact, the 6 Enabled:Unsigned System Integrity Policy (Default) is required and must exist in supplemental policies that are not signed, without that rule option in the supplemental policy whose base policy is also unsigned, would throw an error by the ConvertFrom-CiPolicy cmdlet:

ConvertFrom-CIPolicy: Signed policy is required, but no UpdatePolicySigner is specified.

Copy link
Contributor

Learn Build status updates of commit 5de76c4:

✅ Validation status: passed

File Status Preview URL Details
windows/security/application-security/application-control/windows-defender-application-control/design/select-types-of-rules-to-create.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@aczechowski aczechowski requested a review from jgeurten May 17, 2024 23:46
@jgeurten
Copy link
Contributor

Good catch, @HotCakeX

@HotCakeX
Copy link
Contributor Author

Thank you 🙏

@aczechowski aczechowski merged commit ef39657 into MicrosoftDocs:public May 20, 2024
2 checks passed
@HotCakeX HotCakeX deleted the patch-1 branch May 20, 2024 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants