Picture a 300-seat contact centre in Coimbatore, which we will call Kovai Connect. Tomorrow morning an external auditor arrives for a yearly ISO 27001 check. The operations head, Lakshmi, has been told the certificate is the reason a Swiss insurance client signed with them. She has also been told it can be withdrawn. Let us follow her day to understand what the standard is and what it is not.
What the certificate certifies
ISO/IEC 27001 is an international standard for an information security management system, or ISMS. The key word is management system. It does not list the exact firewall you must buy. It asks whether the organisation identifies its information risks, chooses controls to deal with them, runs those controls, checks that they work and keeps improving. A certification body, accredited and independent, audits this. If it passes, the organisation receives a certificate for a defined scope, valid for three years, with surveillance audits in between, usually yearly.
Scope matters. Kovai Connect’s certificate may cover “the Coimbatore site, insurance support process” and nothing else. A client reading “ISO 27001 certified” on a brochure should ask: which site, which services, which dates?
Morning: the paperwork the auditor reads first
The auditor starts with the risk assessment and the Statement of Applicability. The second one is a list of the controls in Annex A of the standard, each marked as applied or excluded, with a reason. The current edition (2022) groups 93 controls into four themes: organisational, people, physical and technological. The earlier 2013 edition had 114 controls in 14 groups, so check which edition your client expects.
Lakshmi’s team has excluded one control about software development, since they do not write software for clients. The auditor accepts this, because the reason is written down. If they had excluded the control on removable media without a reason, the next questions would be uncomfortable.
Midday: the floor walk
Now the auditor walks the floor, and this is where agents become part of the audit. Expect questions of these types, asked of ordinary staff:
- “What do you do if you see a visitor without a badge?”
- “Where would you report a suspected data leak?”
- “Can you show me how your screen locks?”
- “Is there any paper on your desk? What happens to it at shift end?”
Nobody is expected to recite clause numbers. The auditor is checking whether policy has reached the person doing the work. A beautiful policy that agents have never heard of is a nonconformity waiting to be written.
Then physical checks: access doors, visitor register, CCTV coverage and retention, clean desk, mobile phones in secure areas, and who can enter the server room.
Afternoon: samples and evidence
Auditors work by sampling. They pick a few people who joined recently and ask for their background verification and signed confidentiality undertaking. They pick a few who resigned and ask when system access was removed. They pick a patch cycle and ask for proof of what was installed and when. They look for a recent internal audit, a management review meeting with minutes, and an incident register with actual entries.
An empty incident register worries them more than a short one. A site with 300 people and zero reported incidents in a year suggests that staff do not report, not that nothing happened.
Say the auditor asks for access-removal evidence for ten leavers and finds that two had email access for nine days after the last working day. This is a finding. Findings are graded, commonly as major or minor nonconformities. A minor one needs a corrective action plan with root cause. Several minors in one area, or a major, can delay or suspend the certificate. The exact consequences follow the certification body’s rules.
Why Lakshmi’s client cares
The Swiss client cannot inspect every BPO personally. Certification gives them independent assurance that a system exists and is being run, and it eases their own regulator conversations. It is not a guarantee of no breach. It also does not replace specific demands: a bank may still audit you directly, and a payment client will ask for PCI DSS separately, because card data has its own standard.
Getting ready without theatre
The temptation in the final week is to polish: re-print policies, brief agents with answer sheets, hide the sticky notes. Experienced auditors can tell. The better approach is dull and continuous. Run the leaver checks every month. Record the incidents. Hold the management review on schedule. Do the internal audit properly and fix what it finds. Then audit day is a sample of work you already do.
Lakshmi ends the day with two minor findings, both about late access removal, and a deadline to submit corrective actions. She is not happy, but she knows what to fix, and the certificate stands.
Figures and names in the examples are illustrative.
Leave a Reply