Silent Drop: UFW Firewall Role From The Silent Architect

If you read GhostWare, you already know:

The surface is the battlefield.
Noise is the enemy.

Firewalls should not be a puzzle.
They should be a decision.

A firewall is not complexity.
A firewall is posture.

This is where UFW proves its value.

UFW – The Minimalist Shield

It does not pretend to be a next-generation anything.
It does not promise magic.

It gives you:

Clean rule sets.
Predictable defaults.
A stable, battle-tested foundation.
Behavior that's easy to audit.

Nothing more.
Nothing less.

Small and medium systems don't need enterprise-grade bloat.
Most vendors sell fear packaged as complexity.

UFW fits GhostWare because it does one thing: it enforces.

Ansible – The Operational Hand Of DeadSwitch

Ansible keeps the infrastructure honest.

It removes drift.
It applies intent.

The GhostWare prefers tools that behave the same way every time.
Ansible earned that trust.

The UFW Role – A Silent Drop For Real Systems

Firewalls change.
Rules accumulate.
Mistakes happen quietly.

This role brings order:

Deny incoming by default.
Allow outgoing by default.
Define rules explicitly.
Apply them idempotently.
Deploy the same posture everywhere.

The role is open-source.
Transparent. Inspectable. Adaptable.

DeadSwitch UFW Role on GitHub

Audit it.
Use it.
Extend it.
Break it if you can - and improve it.

Example – Declaring Intent With Precision

-  name:  Deploy UFW firewall
   hosts: all
   become:  true
   roles:
    -  role: ds-ufw
       vars:
         ufw_default_incoming_policy:  "deny"
         ufw_default_outgoing_policy:  "allow"
         ufw_rules:
          - {  port:  "22",  proto:  "tcp",  rule:  "allow" }
          - {  port:  "80",  proto:  "tcp",  rule:  "allow" }
          - {  port:  "443",  proto:  "tcp",  rule:  "allow" }

No over-engineering.
No abstraction layers stacked without purpose.

Just clarity.
Just intent enforced.

Stay disciplined.
Stay sharp.

[ Fear the Silence. Fear the Switch. ]