The Blueprint

Networks and online services.

Your networks, email and cloud services: firewalls, remote access, Wi-Fi, filtering email and stopping others forging it, setting up cloud services securely, and knowing everything you expose to the internet.

NET 23 requirements

Foundation

RW-NET-01A firewall at the internet edge

What
Put a firewall, or the equivalent network rules in your cloud services, between your networks and the internet, set to block every incoming connection that you haven't specifically approved.
Why
Most systems in an office, a data centre or a cloud network were never meant to be reached from the internet, so blocking unrequested connections at the boundary hides them from the constant automated scanning that looks for easy targets.
Protects
Confidentiality · Integrity · Availability

RW-NET-02A firewall on every computer

What
Turn on the built-in firewall of every laptop, desktop and server, set to block incoming connections that haven't been approved.
Why
Laptops are often used on home, hotel and café networks with no office firewall in front of them, so their own firewall stops other devices on the same network from reaching them directly.
Protects
Confidentiality · Integrity · Availability

RW-NET-03Network equipment admin pages kept off the internet

What
Make the admin pages of firewalls, routers and other network equipment unreachable from the internet, unless reaching them also needs a second factor, and manage the equipment only over encrypted connections.
Why
The admin pages of network equipment control everything that passes through it, so keeping them out of reach from outside stops attackers guessing passwords or using flaws in the equipment to take it over.
Protects
Confidentiality · Integrity · Availability

Read the guide: What you expose to the internet, and how you know

RW-NET-04Remote access through one managed gateway

What
Allow remote access to internal systems only through a managed gateway that receives every security update, never by opening services such as remote desktop directly to the internet.
Why
Remote desktop and similar services left open to the internet are among the most common ways ransomware gangs get in, so sending every connection through one managed, protected gateway gives attackers far less to aim at.
Protects
Confidentiality · Integrity · Availability

Read the guide: What you expose to the internet, and how you know

RW-NET-05Office Wi-Fi protected

What
Protect every office wireless network with WPA2 or, preferably, WPA3 encryption, and require either a long, unguessable key or each person's own sign-in to join it.
Why
An open or weakly protected wireless network lets anyone within range, even from outside the building, join your network and reach your systems as if they were sitting at a desk.
Protects
Confidentiality

RW-NET-06Incoming email filtered

What
Filter all incoming email for malware, phishing and forged senders before it reaches anyone's inbox.
Why
Email is where most attacks begin, so stopping the bulk of harmful messages before they arrive means staff face far fewer dangerous links and attachments, and have fewer chances to be caught out.
Protects
Confidentiality · Integrity

RW-NET-07Your email domains can't be forged

What
Publish email authentication records (SPF, DKIM and DMARC) for every domain you send email from, and move the DMARC policy to reject once the reports show your genuine email passes.
Why
These records let other mail servers recognise and refuse email that pretends to come from you, which protects customers and suppliers from fraud sent in your name and stops your own staff trusting forged messages that seem to come from colleagues.
Protects
Integrity

RW-NET-08Domains that never send email protected

What
Publish records on every domain you own but never send email from that tell other mail servers to refuse any email claiming to come from it.
Why
Fraudsters like to use domains that send no email, because nobody is watching them, so telling other mail servers to refuse anything sent in their name closes off an easy route to fraud that looks like it comes from you.
Protects
Integrity

RW-NET-09Cloud services set up securely

What
Set up every cloud service you use from an agreed secure baseline.
Why
Cloud services can be reached from anywhere, so a single wrong setting, such as public file sharing or a security feature left switched off, can expose your data to the whole internet, and starting from a known secure set of settings avoids those gaps from the outset.
Protects
Confidentiality

Established

RW-NET-10Network divided into zones

What
Divide your networks, in the office and in the cloud, into separate zones, such as staff devices, servers, guests and equipment that can't be secured, and let only the traffic each zone needs cross into another.
Why
Separation means an attacker who gets onto one device, or a visitor's infected laptop, can't move freely on to everything else, which limits the damage any single compromise can do.
Protects
Confidentiality · Integrity · Availability

RW-NET-11Firewall rules reviewed

What
Review your firewall and cloud network rules regularly and remove any that are no longer needed or whose purpose nobody can explain.
Why
Rules added for a short-term need tend to stay long after they've been forgotten, and each one is a gap in your defences, so regular reviews keep the boundary as tight as you meant it to be.
Protects
Confidentiality · Integrity · Availability

RW-NET-12A current network diagram

What
Keep a current diagram of your networks, including those in the cloud, showing their zones and every connection to the internet, to cloud services and to other organisations.
Why
A current picture of how everything connects shows where data flows and where an attacker could get in, and lets you contain an incident far more quickly because you know what is joined to what.
Protects
Confidentiality · Integrity · Availability

RW-NET-13Harmful websites blocked

What
Block access to known harmful websites and domains from every company device, including when people are working away from the office.
Why
Blocking harmful sites stops staff reaching phishing pages and malware downloads even after they've clicked a bad link, and stops an infected device contacting the attacker's servers.
Protects
Confidentiality · Integrity

RW-NET-14Cloud security duties divided clearly

What
Record, for each cloud service you rely on, which security tasks the provider carries out and which are yours, and give each of yours a named owner.
Why
Many cloud breaches happen because each side assumed the other was handling something, such as backups or access settings, so writing the split down makes sure none of your share is left undone.
Protects
Confidentiality · Integrity · Availability

RW-NET-15Cloud settings kept to the baseline

What
Check the settings of each cloud service against your agreed baseline regularly, and correct any that have moved away from it.
Why
Settings drift as people add features, share files and try quick fixes, so regular checks catch a weakened setting soon after it changes rather than after someone else has found it.
Protects
Confidentiality

RW-NET-16Domains and certificates renewed in time

What
Set your domain names and website certificates to renew automatically, and check renewals are working well before each expiry date.
Why
If a domain lapses, someone else can register it and take over your website and email, and an expired certificate can take a service offline or teach people to click through warnings, so renewing in good time keeps both working.
Protects
Integrity · Availability

RW-NET-17Domains locked at the registrar

What
Lock each of your domains at the registrar, and protect the registrar account with a second factor, so that nobody can move or change a domain without your agreement.
Why
Whoever controls a domain controls the website and email that use it, so locking it stops an attacker, or a registrar tricked by one, from moving it away and redirecting your email and customers.
Protects
Integrity

RW-NET-18Everything exposed to the internet is known

What
Check regularly what your organisation exposes to the internet, and close anything found that isn't on your list of services meant to be reachable.
Why
Forgotten test servers, old websites and devices opened up for a quick fix are favourite targets because nobody is looking after them, so comparing what is really exposed with what should be finds them before attackers do.
Protects
Confidentiality · Integrity · Availability

Read the guide: What you expose to the internet, and how you know

RW-NET-23Approved tools for calls and messages

What
Decide which encrypted calling, video and messaging services staff may use for work, and make sure work conversations stay on them.
Why
Work discussed on personal messaging apps or unencrypted services can be read by others, can't be found when it's needed and leaves with the person. Agreeing the tools keeps conversations protected and in the organisation's hands.
Protects
Confidentiality · Integrity

Advanced

RW-NET-19Outgoing connections limited

What
Block servers and other systems that hold important data from connecting out to the internet, except to the destinations they need.
Why
Limiting where systems can connect to makes it much harder for malware to fetch its tools or send stolen data home, so an attack that does get in is more likely to stall and be noticed.
Protects
Confidentiality

RW-NET-20Protection against floods of traffic

What
Put the internet-facing services you depend on behind a service that absorbs denial of service attacks.
Why
A flood of traffic from many sources can knock a website or online service offline for hours, and a protection service soaks it up so that customers and staff can carry on working.
Protects
Availability

RW-NET-21Web applications shielded

What
Put a web application firewall in front of the websites and web applications that handle sign-ins, payments or personal data.
Why
A web application firewall blocks common attacks, such as attempts to slip database commands or scripts into forms, and gives you cover while flaws in the application itself are found and fixed.
Protects
Confidentiality · Integrity

RW-NET-22Admin work from protected devices

What
Carry out admin work on servers, network equipment and cloud consoles only from dedicated, locked-down devices or a separate management network.
Why
An everyday laptop that browses the web and opens email is easily infected, so keeping admin work on separate, protected devices means malware picked up during normal work can't watch or hijack an admin session.
Protects
Confidentiality · Integrity · Availability