Historically, IT departments had primary responsibility for information security. Today, the situation is far more complex.
Cloud technologies and other remote working tools make it much easier for organisations to operate across multiple geographic regions. A single business process may rely on dozens of systems to move data from one place to another. One weak link can be enough to create a serious problem.
Information security once focused heavily on acquiring a security technology and leaving it in place. It now requires a broader view of confidentiality, integrity and availability. This means ensuring that authorised users can access the information they need, when they need it, while keeping that information accurate and reliable.
ISO/IEC 27001 addresses the confidentiality, integrity and availability principles of information security. In practical terms, information should be accessible only to authorised users, remain reliable and be available when the organisation requires it.
Start by Understanding What Information Needs Protection
Effective security cannot begin until an organisation understands where its information is stored. Customer databases, financial records and employee files are obvious examples. Other systems can be just as important, including document archives, collaboration tools, cloud platforms, support tickets and internal messaging systems.
An asset inventory gives security teams a clearer understanding of which information systems exist and who depends on them.
This does not mean that every individual file needs to be catalogued. The purpose is to identify important systems and information types, then understand the risks associated with them. A security classification can divide documents and data according to their level of sensitivity. For example:
- Publicly accessible information.
- Information used internally for business operations.
- Sensitive customer or employee data.
- Financial data.
- Authentication credentials.
- Commercially sensitive material.
Not every document requires the same level of protection. Applying identical controls everywhere can make security unnecessarily complex.
Access Controls Should Align With Business Needs
One of the oldest, and arguably most useful, security principles is to ensure that employees can access only the information they need to perform their work. The principle is simple, but permission creep is common.
An employee changes departments but retains previous permissions. A contractor receives administrator access for convenience. A shared account remains active after a project has ended. These situations increase risk while adding very little business value.
Identity and access management should cover the full lifecycle of an account. This includes account creation, authentication, permissions and privileged access, as well as the timely removal of accounts that are no longer required. Sensitive systems may also use multi-factor authentication. The aim is not simply to add more login steps. It is to align access with risk.
Integrated Security Controls
Information security is multi-layered. Each layer addresses a different weakness.
| Security Domain | Primary Objective |
|---|---|
| Access control | Restrict access to sensitive information to authorised users |
| Encryption | Protect information in storage and in transit |
| Monitoring | Detect unauthorised or anomalous activity |
| Backups | Support recovery after disruption |
| Patch management | Reduce exposure to known vulnerabilities |
| Fraud controls | Distinguish legitimate use from system abuse |
| Incident response | Limit the impact when an attack succeeds |
The NIST Cybersecurity Framework adopts a layered approach. It focuses on outcomes rather than specific technical tasks and is therefore applicable to organisations of different sizes and types.
A firewall will not address administrators who have unrestricted access to a system. Encryption cannot stop stolen credentials from being used to log in successfully.
Policies are not always followed either, which is where monitoring becomes particularly valuable. Monitoring helps close the gap between what users are permitted to do and what they actually do.
It can capture failed logins, activity at unusual hours, unexpected changes to account permissions and large downloads. It can also identify attempts to access resources that an account does not normally use.
Fraud monitoring adds another layer because malicious activity can sometimes occur within the boundaries of otherwise legitimate system use.
For example, consider a person who creates multiple accounts, with each account meeting standard registration requirements. This activity may still be abusive, but it can be difficult to identify without advanced account-behaviour monitoring.
Tools for multi-accounting fraud detection can combine account information, behavioural patterns and device fingerprinting to identify links between apparently separate users. Frogo also describes device analysis as a way to detect the same device appearing across multiple accounts.
Other areas of security also rely on behavioural monitoring and fraud detection. The broader lesson is that context should always be considered.
Security and the Human Factor
Focusing too heavily on the latest technology is not enough. Decisions made by users also influence the security of an organisation’s data.
An employee may act carelessly, send confidential information to the wrong recipient or store sensitive information in an inappropriate location. In many cases, the underlying cause is not deliberate negligence but poorly designed processes. Training alone does not solve the problem. Employees should understand:
- how to recognise potential phishing attempts;
- how to store sensitive information safely;
- how to report an incident involving a potentially compromised account or device;
- how to verify a request correctly and what to do if verification fails.
Security guidance should be practical and easy to follow. A complicated forty-page policy that few employees remember provides little effective protection.
Backup and Recovery Systems Matter From a Security Perspective
Information can become unavailable for many reasons, including accidental deletion, ransomware attacks and system failures.
Backups provide a recovery option, but the backup process itself should be tested and validated to ensure that information can actually be restored when needed.
Preparation Needs to Come Before Incident Response
No security programme is completely comprehensive. There must always be a plan for what happens when prevention fails. Security responsibilities should be clearly assigned. Someone needs to identify security issues, someone must coordinate containment, and someone must lead the investigation. Decisions need defined escalation paths, while communication responsibilities should be agreed in advance.
NIST places incident response and recovery alongside detection and prevention because security controls need to work together within a continuous risk-management process. Preparation for routine incidents also makes unexpected events easier to manage.
The Fundamentals Have Not Changed
Technology continues to evolve, but the underlying principles remain familiar. Organisations still need to know what information they hold and protect it appropriately. Access control remains essential. There must be a way to monitor anomalies, and there needs to be a clear plan for responding when something fails.
What has changed is the scale and interconnectivity of modern systems. Corporate environments are increasingly connected, dynamic and dependent on third-party services. Disconnected security measures can create a false sense of protection.
The strongest security programmes combine people, processes and technology. ISO/IEC 27001 approaches information security as an organisation-wide management discipline, treating security controls as part of a broader system rather than as isolated technical measures. That provides the foundation on which more advanced security capabilities can be built.