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

Add policy enforcement for overlay unmounting #1535

Merged
merged 1 commit into from
Oct 7, 2022
Merged

Add policy enforcement for overlay unmounting #1535

merged 1 commit into from
Oct 7, 2022

Conversation

matajoh
Copy link
Member

@matajoh matajoh commented Oct 6, 2022

We previously weren't doing any enforcement around whether an overlay should be allowed to be unmounted. The initial logic is very simple and matches our device unmounting logic:

only allow an unmount if we've seen a mount.

When we get to the hardening PRs, we'll want to revisit this basic rule and decide if we want to make it more vigorous in policy or if we want to put all hardening in GCS or some mixture in-between. That's a design discussion we'll need to have.

@matajoh matajoh requested a review from a team as a code owner October 6, 2022 09:23
@matajoh
Copy link
Member Author

matajoh commented Oct 6, 2022

@anmaxvl @helsaawy

Copy link
Contributor

@helsaawy helsaawy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

pkg/securitypolicy/securitypolicyenforcer.go Outdated Show resolved Hide resolved
We previously weren't doing any enforcement around whether an overlay should be allowed
to be unmounted. The initial logic is very simple and matches our device unmounting logic:

only allow an unmount if we've seen a mount.

When we get to the hardening PRs, we'll want to revisit this basic rule and decide if
we want to make it more vigorous in policy or if we want to put all hardening in GCS
or some mixture in-between. That's a design discussion we'll need to have.

Signed-off-by: Sean T. Allen <seanallen@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
@anmaxvl anmaxvl merged commit 5e27a9b into microsoft:main Oct 7, 2022
@anmaxvl anmaxvl deleted the overlay-unmount branch October 7, 2022 01:54
princepereira pushed a commit to princepereira/hcsshim that referenced this pull request Aug 29, 2024
We previously weren't doing any enforcement around whether an overlay should be allowed
to be unmounted. The initial logic is very simple and matches our device unmounting logic:

only allow an unmount if we've seen a mount.

When we get to the hardening PRs, we'll want to revisit this basic rule and decide if
we want to make it more vigorous in policy or if we want to put all hardening in GCS
or some mixture in-between. That's a design discussion we'll need to have.

Signed-off-by: Sean T. Allen <seanallen@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Co-authored-by: Sean T. Allen <seanallen@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants