Define what shapes your program
A short, structured description of your organization's situation: what influences your security program, who cares about it, and what the program covers.
ISO standards begin here (clauses 4.1–4.3). An auditor's first question is usually "What is in scope and why?"
- Add internal issues (for example "rapid hiring," "legacy systems") and external issues (for example "new privacy laws," "customer demands").
- Add interested parties such as customers, regulators and employees, along with what each expects from you.
- Optionally link each item to related controls, policies and risks.
- Write the scope statement (what the program covers) and the exclusions (what it does not, with reasons).
- Pick which regulations apply (for example GDPR, RBI, SEBI). This turns on the matching regulation features across the product.
- Add a security contact email, which appears on your public Trust Center page.
Northwind lists "Customers require ISO 27001" as an external issue and "Supermarket chains" as an interested party with their expectations.
Who uses itCompliance managers.