bastion

Cybersecurity Standards and Frameworks

Build this skill

Classify an organisation's security activities into the six NIST CSF 2.0 functions and explain what ISO/IEC 27001 certification shows and why compliance alone is not security.

The questionnaire that asks which framework you follow

Tulsi Health has a chance to supply medicines to a large hospital group in Mumbai. Before any price is discussed, the hospital's purchasing team sends a security questionnaire, and two questions stop Vikram Deshmukh cold: "Which cybersecurity framework do you follow?" and "Are you ISO/IEC 27001 certified?" The hospital is not being fussy. It will share patient orders with Tulsi's systems, and it cannot inspect every supplier itself, so it asks whether Tulsi organises its security in a way that others recognise. Security standards and frameworks are those shared, published ways of organising security, so that two organisations that have never met can trust each other's answers.

Why shared rulebooks exist

Think of the ISI mark on a pressure cooker. You do not test the safety valve yourself before buying; you trust that the cooker was checked against a published Indian standard. Security standards work the same way. A standard is a document, agreed by experts and published by a recognised standards body, that sets out requirements an organisation can meet and sometimes be certified against. A framework is a structured way of organising security work, usually as voluntary guidance, which helps an organisation see what it is doing well and where the gaps are.

Without a shared structure, every company invents its own list, and every customer sends a different questionnaire. With one, Neha Kulkarni can say "we follow this framework, and here is where we stand", and the hospital's security team knows exactly what that means. Frameworks also help a small team like Neha's avoid a common trap: spending all its effort on one area, such as antivirus, while ignoring another, such as practising a restore from backup.

The NIST Cybersecurity Framework: six functions

The most widely used framework is the NIST Cybersecurity Framework, or CSF, published by NIST, the United States National Institute of Standards and Technology. It is free to read and voluntary, and organisations of every size around the world use it, not only American ones. Version 2.0, released in February 2024, groups all security work into six functions, the six big jobs every organisation must do. It describes outcomes to reach, such as "staff are trained", rather than products to buy, so it fits a 14-store pharmacy chain as well as a bank.

Identifyknow what you haveProtectguard itDetectnotice attacksRespondact on an incidentRecoverget back to normalGovern: direction,roles, oversight

Govern sits at the centre because it steers the other five: who decides, what matters most and how security is overseen.

Govern sets direction: who is responsible for security, what the company's priorities are, which policies apply, and how risks from suppliers such as Rathi Softech are managed. It was added in version 2.0 to make clear that security is a leadership job, not only an IT one. Identify means knowing what you have and what could go wrong: a list of every laptop, app and database, and which risks matter most. Protect covers the safeguards: two-step login, training, backups, updates. Detect is noticing that something is wrong, for example an alert when a staff login arrives from an unfamiliar city at 2 am. Respond is what happens once an incident is confirmed: containing it, investigating and informing the right people. Recover is getting the business working again and confirming it is safe.

The framework also lets an organisation describe where it stands today and where it wants to be, called its current and target profiles. The gap between the two becomes Neha's to-do list for the year. Try placing real Tulsi Health activities into the six functions below; some look alike, so ask yourself which big job each one does.

ISO/IEC 27001: a management system that can be certified

ISO/IEC 27001 is an international standard published jointly by ISO and IEC, two international standards bodies; the current version is from 2022. Its central idea is the information security management system, or ISMS: a planned, documented way of running security as part of the business. An ISMS means leadership is committed, risks are assessed regularly, controls are chosen to treat those risks, and everything is checked and improved in a repeating cycle, much like the policy loop a careful company already follows.

A security control is any measure that reduces a risk, from a locked cupboard to a password rule. ISO/IEC 27001 comes with a list of 93 controls in its Annex A, grouped into four themes. An organisation does not have to use all 93. It picks the ones its risk assessment calls for and records which it uses and why the rest do not apply.

ISMS: the management systemleadership, risk assessment, review, improvementOrganisational controlspolicies, suppliers, incident handling37People controlsscreening, training, leaving staff8Physical controlslocked rooms, clear desks, equipment14Technological controlslogins, backups, logging, updates34

The management system sits on top and decides which of the 93 Annex A controls, in four themes, the organisation actually needs.

The four themes are a useful way to think about controls even without the standard. Tulsi Health's organisational controls include its policies and its vendor checks. People controls cover training and removing access when someone leaves. Physical controls include the locked server cupboard at Kothrud. Technological controls include two-step login and the nightly backup.

What makes ISO/IEC 27001 different from a framework is certification. An independent certification body sends auditors who check, with evidence, that the ISMS is real and working. If it passes, the organisation receives a certificate, usually valid for three years with smaller check-up audits each year in between. The hospital asked about it because a certificate is evidence checked by an outsider, not just a supplier's own promise.

ISO/IEC 27001 certificate Issued after an independent audit Valid 3 years · yearly check-ups Auditor “Show me the evidence, not the promise.” Neha, IT lead Risk register updated Oct Access review signed, Q3 Restore test log ✓ passed Training records ! 11 pending Each folder proves a control is really working A gap (here, unfinished training) becomes a finding to fix

An audit asks for proof that each control works. The unfinished training records would become a finding that Tulsi Health must fix.

Compliance is a floor, not a finish line

Compliance means meeting the requirements of a law, standard or contract, and being able to prove it. Tulsi Health faces several kinds at once: India's data protection law for its customers' personal data, the card industry's PCI DSS rules for card payments (much reduced because a payment gateway, not Tulsi, handles the card numbers), and whatever the hospital writes into its contract. Knowing which requirements apply, and keeping the evidence ready, is called compliance awareness.

Compliance asksDid you meet the listed rules?Can you prove it on audit day?Checked once or twice a yearSecurity asksCan an attacker get in today?Would you notice, and recover?Tested every single day

A company can pass an audit in March and be breached in April. Compliance sets a minimum; real security keeps going after the auditor leaves.

Being compliant is not the same as being secure. A checklist ticked once a year cannot keep up with attackers who change their methods every month, and a control can exist on paper while nobody actually uses it. Frameworks and standards are best treated as a map that shows where the gaps are, not as a certificate to frame and forget. Neha's honest answer to the hospital, "we follow NIST CSF, here is our current profile, and here is our plan for the gaps", is worth more than a confident "yes" with nothing behind it.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close