Security Governance, Risk and Compliance: ISO 27001, NIST CSF, DPDP

Technical controls protect systems, but governance, risk and compliance (GRC) decides which controls an organisation needs, who is accountable, how much risk is acceptable and how to prove to customers and regulators that the work is done. GRC is also one of the fastest-growing career paths in cyber security, and a good fit for people who enjoy structure, communication and business thinking. This lesson explains the core ideas, the major frameworks and laws (with an Indian context) and gives you exercises to build a small risk register and policy set.

What GRC Means

PartQuestion it answersTypical outputs
GovernanceWho decides, who is accountable and what do we expect?Policies, roles, security strategy, board reporting
Risk managementWhat could go wrong, how likely and how bad, and what will we do?Risk register, risk assessments, treatment plans
ComplianceAre we meeting our legal, regulatory and contractual obligations?Audits, evidence, attestations, certifications

Risk Management: The Essentials

Key vocabulary

TermMeaning
AssetAnything of value: data, systems, people, reputation
ThreatSomething that could cause harm (ransomware group, insider, flood)
VulnerabilityA weakness a threat could use
LikelihoodHow probable it is that the risk event happens
ImpactThe consequence if it does: financial, legal, operational, reputational
Inherent riskRisk before controls
Residual riskRisk that remains after controls
Risk appetiteHow much risk the organisation is willing to accept in pursuit of its goals

The risk management cycle

  1. Establish context: objectives, scope, criteria, risk appetite.
  2. Identify risks: workshops, past incidents, threat intelligence, audits.
  3. Analyse: estimate likelihood and impact (qualitative or quantitative).
  4. Evaluate: compare against appetite to prioritise.
  5. Treat: choose a response (below).
  6. Monitor and review: risks change; review regularly.
  7. Communicate: report in a way decision-makers understand.

The four risk treatments

OptionMeaningExample
Mitigate (reduce)Apply controls to lower likelihood or impactEnable MFA and patch the server
Transfer (share)Move some of the financial impact to another partyCyber insurance, outsourcing with contractual liability
AvoidStop the activity that creates the riskDecide not to store card numbers at all
AcceptKnowingly live with the risk within appetiteMinor risk where the control costs more than the loss

Quantitative risk: a quick example

Quantitative methods express risk in money. Key formulae:

SLE (Single Loss Expectancy) = Asset Value x Exposure Factor
ALE (Annualised Loss Expectancy) = SLE x ARO (Annual Rate of Occurrence)

Example: customer database valued at Rs 50 lakh, a breach would expose 40% (0.4).
SLE = 50,00,000 x 0.4 = Rs 20,00,000
If such a breach is expected once every 4 years, ARO = 0.25
ALE = 20,00,000 x 0.25 = Rs 5,00,000 per year

A control costing Rs 1,50,000 per year that cuts ARO to 0.05 gives
new ALE = 20,00,000 x 0.05 = Rs 1,00,000
Annual benefit = 5,00,000 - 1,00,000 = Rs 4,00,000, which exceeds the cost.

These numbers are estimates and are only as good as their assumptions, but the discipline of writing them down improves decisions. Many organisations combine this with a simple qualitative matrix (likelihood by impact), as in the report-writing lesson.

Policies, Standards, Procedures and Guidelines

DocumentPurposeExample
PolicyHigh-level management intent; mandatory“All access to company systems must use multi-factor authentication.”
StandardSpecific mandatory requirements supporting a policy“Passwords must be at least 14 characters; MFA must use an authenticator app or security key.”
ProcedureStep-by-step instructionsHow to onboard a new employee’s account
GuidelineRecommended good practice; not mandatoryAdvice on creating memorable passphrases

Common security policies: information security, acceptable use, access control, password and authentication, data classification and handling, incident response, backup and recovery, remote working, third-party and supplier security, vulnerability and patch management, secure development, and business continuity.

Major Frameworks and Standards

FrameworkWhat it isUsed for
ISO/IEC 27001:2022International standard for an information security management system (ISMS); certifiable. Annex A of the 2022 edition contains 93 controls in four themesCertification and customer assurance
ISO/IEC 27002:2022Guidance for implementing the controlsImplementation detail
NIST Cybersecurity Framework (CSF) 2.0Voluntary framework with six functions: Govern, Identify, Protect, Detect, Respond, RecoverProgramme structure and communication
NIST SP 800-53Catalogue of security and privacy controlsGovernment and regulated sectors
CIS Critical Security ControlsPrioritised practical safeguardsPractical baseline
SOC 2Attestation report on service organisations’ controls (trust services criteria)SaaS and cloud providers
PCI DSSRequirements for organisations handling payment card dataPayments
COBITIT governance frameworkAligning IT with business objectives
ISO 31000 and NIST SP 800-30Risk management guidanceRisk methodology

Laws and Regulation in India (Overview)

  • Information Technology Act, 2000 and rules: offences such as unauthorised access (section 43/66), identity theft (66C), cheating by personation (66D), cyber terrorism (66F) and liability for failure to protect sensitive personal data; the CERT-In functions and directions, including reporting of incidents within 6 hours and log retention of 180 days.
  • Digital Personal Data Protection Act, 2023: obligations for data fiduciaries, including purpose limitation, security safeguards, breach notification, rights of data principals and penalties; implemented through rules, so check the current status and requirements.
  • Sector regulators: the Reserve Bank of India for banks and payment systems, SEBI for listed companies and market intermediaries, IRDAI for insurance, and TRAI/DoT for telecom each issue cyber security frameworks and reporting rules.
  • Other jurisdictions: GDPR in the European Union, and sector or state laws elsewhere, apply when you serve those customers.

This lesson is educational and not legal advice; consult qualified legal counsel for your situation.

Third-Party and Supply Chain Risk

  • Assess suppliers before onboarding: security questionnaires, certifications (ISO 27001, SOC 2), penetration test summaries.
  • Write security and breach-notification clauses into contracts, plus rights to audit.
  • Limit suppliers’ access to the minimum, and monitor it.
  • Plan for supplier failure: exit strategies and backups.

Security Awareness, Metrics and Reporting

  • Awareness: short, regular, role-based training; phishing simulations used for learning, not punishment; see Social Engineering and Phishing Defence.
  • Metrics: patch compliance, mean time to detect and respond, phishing report rate, number of open high risks, percentage of staff trained, audit findings closed on time.
  • Board reporting: few metrics, plain language, trends, top risks, decisions required.
  • Business continuity and disaster recovery: define RTO (recovery time objective) and RPO (recovery point objective) for each critical service and test them.

Practice Lab 1: Build a Risk Register

For a fictional 50-person company, “Acme Traders”, build a risk register with at least eight risks. Use this template:

IDRiskAssetLikelihood (1-5)Impact (1-5)ScoreTreatmentOwnerResidual
R1Ransomware encrypts file serverFile server3515Mitigate: offline backups, EDR, MFAIT managerMedium
R2Phishing leads to email account takeoverEmail4312Mitigate: MFA, training, mail filteringIT managerLow
R3Supplier breach exposes customer dataCustomer data248Transfer and mitigate: contract clauses, insurance, reviewOperations headMedium

Add five more risks, calculate scores (likelihood times impact), sort by score and write a one-paragraph summary for the managing director.

Practice Lab 2: Write Three Policies

Use a one-page structure for each: purpose, scope, policy statements, roles and responsibilities, enforcement, review date. Draft an Acceptable Use Policy, an Access Control Policy and an Incident Reporting Policy. Ask a non-technical friend to read them: can they tell what is expected of them?

Practice Lab 3: Map Controls to a Framework

  1. Choose six of the technical lessons in this series (for example firewalls, backups, MFA, logging, patching, incident response).
  2. Map each to a NIST CSF 2.0 function and to one or two ISO 27001 Annex A control themes (organisational, people, physical, technological).
  3. Identify which of the six functions has the fewest controls in your imaginary company. That is your gap.

Common Mistakes

  • Treating compliance as security. Passing an audit does not mean you are safe.
  • Writing long policies nobody reads, or copying templates without tailoring.
  • Keeping a risk register that is never reviewed.
  • Failing to define an owner for each risk.
  • Ignoring third-party and supply chain risk.

Practice Exercises

  1. Explain risk appetite using an everyday example such as insurance or driving.
  2. Calculate the ALE for an asset worth Rs 20 lakh with exposure factor 0.5 and an annual rate of occurrence of 0.2.
  3. Describe the difference between a policy, a standard and a procedure for password management.
  4. List the six functions of NIST CSF 2.0 and give one activity for each.
  5. Draft an agenda for a quarterly security report to a board of directors.

Mentor tip: Learn to translate. When you can explain a technical risk in terms of money, customers, law and time, you become the person leadership listens to, and that is how security gets funded.

Educational use only: this overview is general information and not legal or professional advice.

Key takeaways
  • GRC links security work to business objectives, law and accountability.
  • Risk management identifies, analyses, treats and monitors risk: mitigate, transfer, avoid or accept.
  • Policies state intent; standards, procedures and guidelines make them practical.
  • ISO 27001, NIST CSF 2.0, CIS Controls, SOC 2 and PCI DSS are common frameworks; India’s IT Act, CERT-In directions and the DPDP Act matter locally.
  • Compliance is not the same as security; measure real outcomes.

Related Lessons