The Blueprint

Devices, software and vulnerabilities.

The computers, phones, servers and software you rely on: knowing what you have, setting it up securely, keeping it updated, finding and fixing weaknesses, and building software safely if you build your own.

DEV 29 requirements

Foundation

RW-DEV-01A list of every device

What
Keep a current list of every laptop, desktop, phone, server and piece of network equipment you own or manage, including virtual servers in the cloud, with the person responsible for each one.
Why
You can only protect the devices you know about, so a complete list means none of them is left without updates, malware protection or a secure set-up, and a missing or stolen device is noticed quickly.
Protects
Confidentiality · Integrity · Availability

RW-DEV-02A list of the software and services you run

What
Keep a current list of the software installed on your devices and servers, and of the cloud services you use, showing the version of each where it has one and who looks after it.
Why
Knowing exactly which software and versions you run lets you tell straight away whether a newly announced weakness affects you, and makes it easy to spot programs that are unsupported or that nobody approved.
Protects
Confidentiality · Integrity · Availability

Read the guide: The tool that can reach every computer

RW-DEV-03Devices set up securely

What
Set up every device and server from an agreed secure configuration that removes or turns off the software, services and features you don't need, such as programs starting automatically when a USB drive or disc is inserted.
Why
Every unneeded program, service or setting is another way in for an attacker, so starting from a locked-down set-up leaves far fewer weaknesses to exploit and makes every device behave in the same, predictable way.
Protects
Confidentiality · Integrity · Availability

RW-DEV-04Default passwords changed

What
Change every default password, and remove or disable every default account, on devices, software and equipment before they're put into use.
Why
Default passwords and accounts are printed in manuals and listed online, so attackers try them first, and changing them closes one of the simplest ways for anyone to take control of new equipment.
Protects
Confidentiality · Integrity · Availability

RW-DEV-05Security fixes in place within 14 days

What
Install every high or critical security fix for your operating systems, applications and device firmware no more than 14 days after it's released.
Why
Once an update is published, attackers can work out the weakness it fixes and start using it within days, so installing updates quickly closes that window before it can be used against you.
Protects
Confidentiality · Integrity · Availability

RW-DEV-06Unsupported products replaced

What
Replace or remove software and hardware before its maker stops providing security updates for it, and isolate anything that can't yet be replaced.
Why
Once a product stops receiving security updates, every weakness found in it afterwards stays open for good, so replacing it in time stops attackers gaining a permanent way in.
Protects
Confidentiality · Integrity · Availability

RW-DEV-07Malware protection on every computer

What
Run centrally managed malware protection, with current updates, on every laptop, desktop and server.
Why
Malware protection stops most known harmful software before it can run and warns you when something gets through, so a single infected file or website is far less likely to spread or lock up your data.
Protects
Confidentiality · Integrity · Availability

RW-DEV-08Macros blocked except where needed

What
Turn off macros in office documents for everyone who doesn't need them, block macros that arrive from the internet, let only macros you have checked and trust run, and stop users changing these settings.
Why
Documents carrying harmful macros are one of the commonest ways ransomware and other malware arrive by email, so blocking macros from outside removes that route while leaving the trusted ones your work relies on.
Protects
Confidentiality · Integrity · Availability

RW-DEV-09Conditions for devices you don't own

What
Allow personally owned devices, and devices belonging to contractors and suppliers, to reach company data only when they meet conditions you have set, such as a supported operating system, a screen lock and work data kept apart from personal data.
Why
A personal device is outside your direct control, so setting minimum conditions stops an out-of-date or unprotected phone or computer becoming the weak point that exposes your email and files.
Protects
Confidentiality

Established

RW-DEV-10Critical weaknesses fixed within 48 hours

What
Install updates within 48 hours for vulnerabilities that the maker rates as critical, or for which a working exploit exists, when they affect systems that can be reached from the internet.
Why
Once attackers are using a weakness, automated tools search the internet for it within hours, so the systems you expose publicly need fixing far faster than the usual 14 days if they're not to be caught.
Protects
Confidentiality · Integrity · Availability

RW-DEV-11Software installed only with approval

What
Allow software to be installed on company devices only by the IT team or from a list of programs it has approved.
Why
When people can't install whatever they come across, programs carrying malware, unlicensed copies and tools with weaknesses of their own are kept off your devices, and your software list stays accurate.
Protects
Confidentiality · Integrity · Availability

RW-DEV-12Work phones and tablets managed

What
Enrol every phone and tablet used for work in a device management service that can lock it and remove company data from it remotely, and that allows apps only from the official app store or a list you have approved.
Why
Phones and tablets hold email, files and sign-in codes and are easily lost, so managing them centrally lets you enforce basic protection and wipe company data before whoever finds or steals one can use it.
Protects
Confidentiality

RW-DEV-13Removable storage controlled

What
Block USB drives and other removable storage on company devices, or scan anything plugged in automatically, and allow exceptions only for encrypted storage that has been approved.
Why
Removable drives can bring malware in past your email and web protection and can carry large amounts of data out of the organisation unseen, so controlling them closes both routes.
Protects
Confidentiality · Integrity

Read the guide: The memory sticks nobody can account for

RW-DEV-14Vulnerabilities found and fixed

What
Scan your internal and internet-facing systems for known vulnerabilities, daily for those reachable from the internet, and fix each one found within a timescale set by how serious it is, and within one month at most.
Why
Scanning finds the missed updates, weak settings and forgotten systems that slip through day-to-day upkeep, and fixing the most serious first means the weaknesses most likely to be exploited are closed soonest.
Protects
Confidentiality · Integrity · Availability

RW-DEV-15Only approved programs can run

What
Let laptops, desktops and servers run only programs, scripts, installer files, software libraries and drivers that you have approved.
Why
Blocking everything that hasn't been approved stops malware, including new kinds that malware protection doesn't yet recognise, from running even when someone opens a harmful file or link.
Protects
Confidentiality · Integrity · Availability

Read the guide: The tool that can reach every computer

RW-DEV-16Browsers and office software hardened

What
Turn off the features of web browsers, office software and PDF readers that attackers most often misuse, such as old plug-ins, web adverts and office documents starting other programs, allow only browser extensions you have approved, and stop users changing these settings.
Why
These are the programs people use to open content from outside, so switching off the features attackers most often abuse leaves a harmful web page or document far fewer ways to take over a device.
Protects
Confidentiality · Integrity · Availability

RW-DEV-17A secure way of building software

What
Follow a written secure development process for software you build, covering how its security needs are set, how its code is written and how it's checked before release.
Why
Building security in from the start costs far less than fixing weaknesses after release, and having the process written down means the same care is taken on every project, whoever does the work.
Protects
Confidentiality · Integrity · Availability

RW-DEV-18Code checked by a second person

What
Have every change to the code of software you build checked by someone other than its author before it's released.
Why
A second pair of eyes catches security mistakes the author can't see, and makes it much harder for a careless or deliberately harmful change to reach your live systems unnoticed.
Protects
Integrity

RW-DEV-19Software tested before release

What
Test software you build for security weaknesses before each significant release, and fix the serious problems found before it goes live.
Why
Testing before release finds weaknesses, such as broken access checks or forms that accept harmful input, while they're cheap to fix and before attackers or customers come across them.
Protects
Confidentiality · Integrity · Availability

RW-DEV-20Third-party code kept free of known flaws

What
Check the open-source libraries and other third-party components in software you build for known vulnerabilities, and update or replace any that are affected.
Why
Most modern software is largely made of other people's code, so a weakness in one popular component can expose your product to attack even when your own code has no faults.
Protects
Confidentiality · Integrity · Availability

RW-DEV-21Development kept apart from live systems

What
Develop and test software in environments that are separate from your live systems and can't change them.
Why
Keeping development and testing apart means unfinished or faulty code, test accounts and developers' broad access can't damage live services or the data they hold.
Protects
Integrity · Availability

RW-DEV-22Source code and build tools protected

What
Limit who can read and change the source code of software you build, and the tools that build and release it, to the people who currently work on it.
Why
Source code shows how your systems work and where their weak points lie, and anyone who can change it could slip in a hidden flaw, so restricting it to the people actively building the software protects both your secrets and the integrity of what you release.
Protects
Confidentiality · Integrity

RW-DEV-23A way for outsiders to report security concerns

What
Publish a way for customers and others outside the organisation to report security weaknesses or incidents they find in your services, and respond to every report.
Why
Researchers and customers often spot weaknesses first, so a clear route for telling you means you hear about them and can fix them, rather than the details being made public or sold.
Protects
Confidentiality · Integrity · Availability

RW-DEV-27Unknown devices found and dealt with

What
Check your networks regularly for devices that are not on your list of devices, and approve, remove or isolate each one you find.
Why
A device nobody knows about doesn't get updates, malware protection or monitoring, and could be an attacker's own equipment. Finding the devices that aren't on your list closes that blind spot.
Protects
Confidentiality · Integrity · Availability

Advanced

RW-DEV-24Configuration watched for drift

What
Check devices and servers automatically against your agreed secure configuration, and correct any that have drifted from it.
Why
Settings change over time through fixes, installs and quick workarounds, so checking all the time catches a weakened device soon after it changes rather than at the next periodic review.
Protects
Confidentiality · Integrity · Availability

RW-DEV-25Independent attempts to break in

What
Have an independent specialist try to break into the software you build, the systems you expose to the internet and your internal network, and fix the weaknesses they find.
Why
Specialists think like attackers and find combinations of weaknesses that scans and your own testing miss, which shows you how a determined attack would actually get in before a real one does.
Protects
Confidentiality · Integrity · Availability

RW-DEV-26Updates rolled out in stages

What
Roll out significant software and security updates to a small group of systems first, and extend them to the rest once they've proved sound.
Why
A faulty or tampered update pushed to every machine at once can stop the whole organisation within minutes, as several worldwide outages have shown, whereas a staged rollout confines the damage to a few systems and leaves time to halt it.
Protects
Integrity · Availability

RW-DEV-28Scripting tools restricted and recorded

What
Remove old versions of command-line and scripting tools such as PowerShell, limit what people without admin rights can do with them, and log the commands they run.
Why
Attackers use the scripting tools built into every computer to run their commands without installing anything that malware protection might catch. Restricting those tools, and recording how they're used, takes away one of their favourite methods and leaves a trail if they try.
Protects
Confidentiality · Integrity

RW-DEV-29Prepared devices for high-risk travel

What
Give people travelling to countries where devices are at particular risk a device prepared for the trip, holding only what they need, and check it before it reconnects on their return.
Why
In some countries devices can be searched, copied or tampered with at the border or in hotels. A device carrying only what the trip needs limits what can be taken, and checking it on return stops anything planted on it reaching your network.
Protects
Confidentiality · Integrity