Content update

[jtdauria-shi]

• Onboarding documentation
• Policy structure
• Update Zensicle

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	zensical@​0.0.51 ⏵ 0.0.53

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical-0.0.53/python/zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (zensical/templates/assets/javascripts/LICENSE) License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: pypi zensical under unrecognized license License: unrecognized license - This license was not allowed or given any lesser classification by the applicable policy (zensical/templates/assets/javascripts/LICENSE) License: Font-Awesome-Free-License-6.x - The applicable license policy does not permit this license (5) (zensical/templates/.icons/fontawesome/LICENSE.txt) From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential security risk (AI signal): pypi zensical is 65.0% likely risky Notes: This fragment is primarily a configuration parser, but it contains security-relevant design choices that can become malicious impact if an attacker can control configuration inputs: it uses yaml.load with a potentially unsafe Loader and supports dynamic importing/calling of callables specified by dotted strings from config (_resolve + invocation in multiple extension hooks). It also imports modules listed in macros config (importlib.import_module) with side effects. If configs/themes/macros are trusted, risk may be acceptable; if untrusted, this is effectively a code-execution primitive. The snippet also appears truncated/buggy at the end (_convert_plugins returns an undefined variable), so additional context is needed for a complete assessment. Confidence: 0.65 Severity: 0.70 From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What are AI-detected potential security risks? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Potential security risk (AI signal): pypi zensical is 65.0% likely risky Notes: This fragment is primarily a configuration parser, but it contains security-relevant design choices that can become malicious impact if an attacker can control configuration inputs: it uses yaml.load with a potentially unsafe Loader and supports dynamic importing/calling of callables specified by dotted strings from config (_resolve + invocation in multiple extension hooks). It also imports modules listed in macros config (importlib.import_module) with side effects. If configs/themes/macros are trusted, risk may be acceptable; if untrusted, this is effectively a code-execution primitive. The snippet also appears truncated/buggy at the end (_convert_plugins returns an undefined variable), so additional context is needed for a complete assessment. Confidence: 0.65 Severity: 0.70 From: requirements.txt → pypi/[email protected] ℹ Read more on: This package | This alert | What are AI-detected potential security risks? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[Copilot]

Pull request overview

This PR updates SHIELD documentation structure by reorganizing the nav, replacing the old “Required Graph API Permissions” doc with a new “Application Permissions” page, consolidating Conditional Access policy docs into a single “Entra Conditional Access” reference page, and bumping the zensical version used to build the site.

Changes:

• Updated zensical.toml nav to reflect new prerequisite pages and a new “Policies” section under Deploy reference.
• Replaced the removed “Required Graph API Permissions” page with a new “Application Permissions” page and updated an internal link.
• Consolidated many Conditional Access policy pages into Entra-Conditional-Access.md and updated the docs tool version in requirements.txt.

Reviewed changes

Copilot reviewed 26 out of 27 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
zensical.toml	Updates site navigation to new prerequisites and the new Deploy → Reference → Policies structure.
requirements.txt	Bumps zensical from 0.0.51 to 0.0.53.
docs/SHIELD/Reference/Settings/Configure-Managed-Identity.md	Updates the permissions doc link to point to the new page.
docs/SHIELD/Prerequisites/Required-Graph-API-Permissions.md	Removes the old permissions page.
docs/SHIELD/Prerequisites/Network-Traffic-Inspection.md	Adds a new prerequisite page describing network traffic inspection constraints.
docs/SHIELD/Prerequisites/Installation.md	Rewrites installation/onboarding steps and networking requirements text.
docs/SHIELD/Prerequisites/index.md	Expands prerequisites landing page with pricing/security/data-structure content and reorganized sections.
docs/SHIELD/Prerequisites/Application-Permissions.md	Adds the replacement permissions page and permission tables.
docs/SHIELD/Deploy/Reference/Policies/Entra-Conditional-Access.md	Adds consolidated Conditional Access policy documentation.
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/User-Risk.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Token-Binding.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Sign-In-Risk.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Session-Persistence.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/OS-Enforcement.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/MFA.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Location.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Legacy-Auth.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Join-Type.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Hardware-Enforcement.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Disable-CA-Resilience-Downgrade.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Compliance.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Block-Non-Priv.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Privileged/Conditional-Access/Authentication-Methods.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Enterprise/Conditional-Access/MFA.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Enterprise/Conditional-Access/MDCA.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Enterprise/Conditional-Access/Location.md	Removes legacy per-policy page (now consolidated).
docs/SHIELD/Deploy/Reference/Architecture/SHIELD/Enterprise/Conditional-Access/Compliance.md	Removes legacy per-policy page (now consolidated).

Suppressed comments (2)

docs/SHIELD/Prerequisites/Application-Permissions.md:89

• Same admonition formatting issue as above: the unindented blank line after !!! note may break rendering (and turn the following indented text into a code block).

!!! note

    `Policy.Read.All` is necessary due to a known issue with the current Graph API, in the future `Policy.ReadWrite.ConditionalAccess`/`Policy.Read.ConditionalAccess` will be all that is necessary.
    See this link for Microsoft's official statement: [Graph API Known Issues Portal](https://developer.microsoft.com/en-us/graph/known-issues/?search=13671)

docs/SHIELD/Prerequisites/Application-Permissions.md:80

• Typo: “license lability” should be “license liability”.

    | [`SecurityIdentitiesAccount.Read.All`](https://learn.microsoft.com/en-us/graph/permissions-reference#securityidentitiesaccountreadall){:target="_blank"}                                                                                                                   | ✅                | Used in Discover to measure the Defender for Identity license lability.                                                                                                                                                                                                                                               |

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.