Skip to content

Conversation

@jackhodgkiss
Copy link
Contributor

Add a new stack for managing the security baseline expected of new and existing deployments.

[skip ci]

Add a new `stack` for managing the security baseline expected of new and
existing deployments.

[skip ci]
# the default zone will not be changed.
# Predefined zones are listed here:
# https://firewalld.org/documentation/zone/predefined-zones.html
compute_firewalld_default_zone: trusted
Copy link
Member

Choose a reason for hiding this comment

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

We should ideally default to drop here, though it does make it trickier to apply

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had just taken everything from the docs.

Need to figure out how to manage networks and their zones within this setup.

Copy link
Member

Choose a reason for hiding this comment

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

We should probably update those docs. I don't think that the firewall will really do anything if the default zone is trusted. Basically that just means if there's no specific rule, it just passes, which is pretty insecure.

The easiest way to manage this right now is to just set *_firewalld_default_zone: "{{ stackhpc_firewalld_default_zone }}"

Then I don't mind whether we set stackhpc_firewalld_default_zone to trusted or drop, as long as we include a decent comment next to it explaining what it does

Copy link
Member

Choose a reason for hiding this comment

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

Actually, I might be wrong. I need to dig into this more

@jackhodgkiss jackhodgkiss marked this pull request as ready for review December 7, 2025 15:41
@jackhodgkiss jackhodgkiss requested a review from a team as a code owner December 7, 2025 15:41
@jackhodgkiss jackhodgkiss requested a review from axelsimon January 7, 2026 17:02
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.

3 participants