The Blueprint

Legal, regulatory and contractual.

The legal, contractual and regulatory duties that apply to you: knowing what they are, data protection and privacy, card payments, licences and records, and checking, internally and from outside, that you meet them.

LAW 21 requirements

Foundation

RW-LAW-01Know what the law and your contracts require

What
Keep a list of the laws, regulations and contract terms on security and data protection that apply to your organisation, with an owner for each.
Why
You can only meet obligations you know about, and a maintained list with owners makes fines, lost contracts and broken promises to customers far less likely to come as a surprise.
Protects
Confidentiality · Integrity · Availability

RW-LAW-02Someone responsible for data protection

What
Name a person who is responsible for how the organisation meets its duties under data protection law, and make sure staff know who it is.
Why
Personal data brings legal duties and the risk of real harm to people, so having one person who understands those duties, and whom staff can turn to, means questions, requests and problems are handled properly and quickly.
Protects
Confidentiality

RW-LAW-03People told how their data is used

What
Give people a clear, plain-language notice that explains what personal data you collect about them, why you need it, who you share it with and how long you keep it.
Why
Being open about how you use personal data is a legal duty in most countries, and writing an accurate notice makes you work out exactly what you do with that data, which is the starting point for protecting it.
Protects
Confidentiality

RW-LAW-04Requests about personal data answered on time

What
Log every request from a person to see, correct or delete their personal data, and answer each one within the time the law allows.
Why
Answering these requests properly and on time keeps you within the law and avoids complaints to the regulator, and a log of every request means none is lost or forgotten when someone is away.
Protects
Confidentiality

RW-LAW-05Privacy assessed before high-risk uses of data

What
Assess the privacy risks of any new use of personal data that could seriously affect people before it begins, and put in place the protections the assessment calls for.
Why
Finding privacy risks before a project starts means safeguards can be designed in instead of added after harm has been done, and in many countries the law requires this assessment for high-risk uses.
Protects
Confidentiality

RW-LAW-06Personal data sent abroad only lawfully

What
Check that the law allows each transfer of personal data to another country, including making it reachable from one, and put any safeguards the law requires in place before the transfer happens.
Why
Data protection laws often limit where personal data may go, so checking each transfer first keeps the data under proper protection and avoids a breach of the law that might only come to light after an incident.
Protects
Confidentiality

RW-LAW-07Card payments taken safely

What
Take card payments only through a payment provider that is certified against the card industry's security standard.
Why
Passing card details straight to a certified provider keeps them out of your own systems, which greatly reduces what an attacker could steal from you.
Protects
Confidentiality

RW-LAW-08Card security self-assessment completed

What
Complete the card security self-assessment each year if your bank or payment provider asks you to.
Why
The self-assessment makes you check that your own website, devices and staff aren't putting card details at risk, and keeping it current avoids penalties or losing the ability to take cards.
Protects
Confidentiality

Established

RW-LAW-09Customer security commitments kept

What
Check regularly that you are still meeting the security commitments you have made in your customer contracts, and put right any you are not.
Why
Customers rely on your security as part of their own, so confirming you still deliver what you promised protects both their information and your contracts.
Protects
Confidentiality · Integrity · Availability

RW-LAW-10A record of how personal data is used

What
Keep a record of each way you use personal data, setting out its purpose, the kinds of data and people involved and the legal basis that allows it, including the extra condition the law requires for sensitive kinds such as health data.
Why
A complete record shows you where personal data goes and why, so nothing is collected or kept without a reason, and lets you show a regulator that every use is lawful.
Protects
Confidentiality

RW-LAW-11Software and content used within licence

What
Use software, and material that belongs to others such as images, fonts and text, only within the terms of the licences you hold.
Why
Staying within licence terms avoids legal claims and audit penalties, and keeping track of what you are licensed for also brings to light unknown or pirated software, which is a common way for malware to get in.
Protects
Integrity

RW-LAW-12Required records kept safe

What
Protect the records you are required to keep, such as financial, employment and contract records, against loss, alteration and unauthorised access for as long as you must keep them.
Why
If required records are lost or quietly changed you may be unable to prove what happened in a dispute, an audit or an investigation, so protecting them keeps them complete and trustworthy when you need them.
Protects
Integrity

RW-LAW-13Checks that policies are followed

What
Check regularly that your security policies are actually being followed in day-to-day work, and put right any gaps you find.
Why
A policy that is written down but ignored gives false comfort, so routine checks show where practice has slipped and let you correct it before an attacker or an auditor finds the gap.
Protects
Confidentiality · Integrity · Availability

RW-LAW-14Internal audit of security

What
Audit your security arrangements against your own policies, and any standard you have committed to, on a planned cycle, using people who are not auditing their own work.
Why
An impartial, planned audit finds weaknesses that the people running a process are too close to see, and gives leadership and customers good grounds to trust that your controls work as described.
Protects
Confidentiality · Integrity · Availability

RW-LAW-15Sector regulators' requirements met

What
Identify the security assessments and returns your sector regulators expect from you, and submit each one complete and on time.
Why
Sector regulators set security expectations around the particular harm a failure in your sector could cause, so meeting them protects the people who depend on you as well as your permission to operate.
Protects
Confidentiality · Integrity · Availability

RW-LAW-16Export rules checked before technology is shared

What
Check whether export controls apply before you send technical information, software or technology abroad or share it with foreign nationals, and obtain any licence needed before you do.
Why
Some technical information, particularly in defence, aerospace and advanced technology, may only be shared across borders with a licence, so checking first avoids serious criminal and commercial penalties and keeps sensitive technology out of the wrong hands.
Protects
Confidentiality

RW-LAW-17Audits and tests on live systems agreed first

What
Agree the scope, timing and access for any audit or technical test of live systems with the system's owner before it starts.
Why
Audits and tests on live systems can slow or interrupt services and expose sensitive data, so settling the arrangements beforehand means you gain the assurance without causing an outage or a leak of your own making.
Protects
Availability

RW-LAW-20Personal data protected by design

What
Build data protection into every new system, process or change that uses personal data, so that it collects and keeps only the personal data needed for its stated purpose and its settings protect privacy by default.
Why
Personal data you don't collect can't be lost or misused, and protection designed in from the start is more reliable than protection added later. Data protection law in many countries requires both.
Protects
Confidentiality

RW-LAW-21Requests for data from authorities checked

What
Check that every request from the police, a regulator or another authority to hand over information is genuine and lawful before you respond, disclose only what it requires, and record each request and your response.
Why
Criminals pose as the police or regulators to get personal data handed over, and even genuine requests have limits. Checking each one, and disclosing only what it requires, protects the people whose information you hold, and you.
Protects
Confidentiality

Advanced

RW-LAW-18Security reviewed from outside

What
Have a qualified, independent auditor or adviser review how you manage information security, both on a regular cycle and after major changes.
Why
Someone from outside with no stake in the result will see blind spots and comfortable assumptions that internal reviews tend to miss, giving leadership an honest view of where you really stand.
Protects
Confidentiality · Integrity · Availability

RW-LAW-19Coming changes in the law tracked

What
Watch for new and changing laws and regulations on security and data protection that will affect you, and plan the work needed to meet them before they take effect.
Why
New obligations often take months to meet, so spotting them early gives you time to prepare properly, rather than rushing changes through or finding yourself out of step on the day a law comes into force.
Protects
Confidentiality · Integrity · Availability