ESSENTIAL GUIDANCE · FOUNDATION GUIDE · 3 min read

Part of Foundation insights →

Firewall configuration best practices

Learn how to limit unnecessary network access, document firewall rules and review them when systems change.

Technical review lead: James Hinton · Offensive security lead

A firewall controls which traffic can enter or leave a network. Start by recording why each rule is needed and who owns it. Review the rules after major changes and on a regular schedule.

Need an acronym translated?Open the cyber glossary →

Start with the business need for every route

For each firewall rule, record the traffic it allows and which service or users need it. Add the environment, the owner and the next review date. If nobody can explain why the rule exists, check how it is used before changing it.

Default-deny reduces accidental exposure

A default-deny approach permits only traffic that has been explicitly authorised. Keep allowed sources, destinations, ports and protocols as narrow as the service permits, and avoid broad ranges or universal sources where a more specific rule will work. Confirm the requirement with the system owner before changing production access.

Separate administration from public service access

Keep admin access separate from public access. Use a controlled route and strong authentication for the people who manage the service. Review temporary access for suppliers and emergency support. Remove it when the work ends, following your change process.

Remove obsolete and duplicated rules

Applications move, suppliers change and temporary projects end, but the related rules often remain. Review rules against current assets and service dependencies, identify duplicates and shadowed entries, and remove obsolete access through an authorised change process. Preserve enough evidence to explain what changed and why.

Review firewall rules and cloud controls together

Cloud security groups, network access controls, web application firewalls and platform policies can create overlapping paths. Review them together rather than assuming one control compensates for another. An apparently restricted perimeter rule may be undermined by a public cloud endpoint or a permissive identity policy.

Keep logs that help you investigate activity

Firewall logs should help teams confirm expected use and investigate suspicious activity without collecting data without purpose. Define which events matter, retain them for an appropriate period and make sure monitoring teams can distinguish routine traffic from denied connections, unusual administration and unexpected changes.

Review after change and at a defined interval

Material releases, infrastructure moves, new suppliers and incident findings should trigger a targeted rule review. Periodic review remains necessary for quieter environments. Record the reviewer, evidence considered, exceptions retained and the next review date so the control can be demonstrated rather than assumed.

Validate changes and retain a recovery route

Test material rule changes through the organisation’s authorised change process before relying on them in production. Record the previous configuration, validation performed and the route for reversing the change if legitimate access is disrupted. A technically narrower rule is not an improvement if it unexpectedly prevents an essential service from operating.

Connect firewall hygiene to Cyber Essentials

Cyber Essentials includes firewalls and internet gateways among its five core control areas. Preparation requires an accurate scope and defensible configuration across relevant devices and services. Pentesys Foundation can support scope definition, readiness review and evidence preparation; it does not provide managed firewall administration.

TALK TO PENTESYS

Apply this guidance to your environment.

Tell us what you need to understand, test or prove. We'll help you choose a proportionate next step—without forcing the conversation into a predefined package.

Discuss your Cyber Essentials readiness →Explore Foundation

Keep reading

Pentesys trust and assurance

Recognised credentials. Responsible AI. Experienced people.

Clear evidence of our company standards, testing services and access to AI programmes.

Independent company assurance

CREST member company for Penetration Testing in EMEA

CREST member company

Penetration Testing in EMEA. Company standards independently assessed by CREST.

Valid until 1st November 2027View company certificate
CREST Security Testing accreditation for penetration testing

CREST-accredited human-led penetration testing

Independent assurance for Pentesys’s human-led penetration-testing service.

Human-led testingView CREST listing

AI-enabled testing assurance

CREST accreditation for AI-enabled penetration testing

CREST-accredited AI-enabled penetration testing

Pentesys is one of the first ten companies worldwide accredited by CREST for AI-enabled penetration testing. The accreditation assesses the responsible, secure and appropriate use of AI in penetration-testing services.

AI-enabled penetration testingView CREST announcement

Responsible-AI commitment

CREST AI Charter signatory

CREST AI Charter signatory

A separate commitment to responsible, transparent and accountable use of AI in cybersecurity.

Responsible-AI commitmentAbout the CREST AI Charter

Secure organisational baseline

Cyber Essentials certified

Cyber Essentials certified

Pentesys is certified across the whole organisation against the Cyber Essentials baseline controls.

Recertification due 12 August 2027View Cyber Essentials certificate

Controlled AI programme access

Pentesys participates in Anthropic’s Cyber Verification Program (CVP) for Claude and has approved access to OpenAI Daybreak Blue.

Anthropic CVP for Claude

Participation in Anthropic’s Cyber Verification Program.

Programme participationAbout Anthropic CVP

OpenAI Daybreak Blue

Approved access for defensive cybersecurity work.

Approved programme accessAbout Daybreak Blue

CREST accreditation applies to Pentesys’s service delivery, not to an AI model, the Portal or an appliance.

Meet the expertise behind our testing