Repository navigation
feat(enforcement): inspect protected enrollment without granting launch - #802
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The session helper can now inspect a protected enrollment through the fixed
--inspect-enrollmentcommand. It retains and checks the installation's ancestors, root, record and executable, refusing unavailable identity, unsafe effective permissions, malformed records, mismatched hashes and uncertain cleanup. The command returns a bounded observation and keeps ownership, caller and launch qualification false.The existing probe/prepare protocol is preserved. This introduces no installer, service, VM operation or production launch permission. The documentation distinguishes protected-observation models from native held-file controls and explains the process-supervision requirement.
Validation: independent Astra requirements/security review of the frozen seven-file implementation; integrated Windows sidecar build; 54/54 tests across inspection and existing framed-protocol suites; scoped ESLint. Required GitHub CI contexts must pass before merge.