Most security failures do not start with an advanced attack. The UK National Cyber Security Centre puts it simply: “most cyber-attacks are basic in nature - the digital equivalent of a thief trying your front door to see if it’s unlocked.” NCSC: Cyber Essentials overview
Its Cyber Essentials scheme reduces the baseline to five technical controls, “designed to prevent the most common internet based cyber security threats”. It is a UK scheme, but the five controls make a practical checklist for any business, wherever it operates.
In India, the baseline comes with a reporting clock
CERT-In’s directions of 28 April 2022 add two obligations that the baseline alone does not cover. Service providers, intermediaries, data centres, body corporates and Government organisations must report the listed cyber incidents to CERT-In “within 6 hours of noticing such incidents”, and must keep logs of all their ICT systems “for a rolling period of 180 days”, maintained within Indian jurisdiction. CERT-In directions, 28 April 2022
In practice that means knowing in advance who decides an incident is reportable, where the logs are and who can retrieve them at short notice. Our article on CERT-In incident reporting covers that decision path in detail.
The five controls below are the baseline those duties sit on. Each one also produces the evidence you will need if an incident has to be reported.
1. Control what can reach your systems
Firewalls and internet gateways decide what traffic gets in and out. Close every port and service that has no business reason to be open, change default administrator passwords on network devices, and review the rules whenever a system is added or retired.
2. Configure systems securely
Devices and software arrive configured for convenience, not security. Remove unused accounts and applications, change default credentials, and turn off features such as automatic running of downloaded files. Keep a standard build so new devices start secure.
3. Apply security updates promptly
Unpatched software is one of the most common ways in. Keep an inventory of what you run, apply security updates on a defined timetable, and replace software that no longer receives updates. Treat internet-facing systems as the first priority.
4. Control who has access
Give each person only the access their role needs. Keep administrator accounts separate from everyday accounts, turn on multi-factor authentication, and remove access promptly when people change role or leave.
5. Protect against malware
Use anti-malware protection on every device that supports it, keep it updated, and limit which applications can run. Pair it with backups that are kept separately and tested, so recovery does not depend on the infected systems.
Make each control reviewable
A control only helps if someone can show it is working. For each of the five, name an owner, decide what evidence proves it (a firewall rule review, a patch report, an access review) and check it on a set schedule. That record is also what customers, auditors and insurers increasingly ask to see.
A simple starting set of evidence for each control:
- Firewalls: the current rule set, with an owner and business reason for every open port, and the date of the last review.
- Secure configuration: the standard build for each device type and a record of exceptions.
- Security updates: an inventory of software in use and a patch report showing time from release to installation.
- Access control: a list of administrator accounts, MFA coverage and the last joiner, mover and leaver review.
- Malware protection: coverage across devices, the date of the last successful backup restore test and any devices without protection.
If any of these cannot be produced within a day, that gap is the first thing to fix. It is usually cheaper to close than a new tool, and it is what an incident or an audit will test first.

