Our cyber security products span from our next gen SIEM used in the most secure government and critical infrastructure environments, to automated cyber risk reporting applications for commercial and government organisations of all sizes.
This blog looks at the increasing volume and frequency of software upgrades and explores how your information security team can take control of the change process and improve situational awareness.
Roadworks ultimately improve the quality of a road and potentially its effectiveness, however initially it adds risk to road users. Just like roadworks, system upgrades require close monitoring and change management.
The rate at which vendors publish patches and software upgrades has dramatically increased in recent years, with businesses gaining the benefit of these continuous cycles of product improvement. These changes improve systems, their performance and their capabilities. Yet, they also introduce operational risk: information security managers are asking how they can satisfy this growing demand for change and yet maintain the security of their systems and data?
An Information Security Management System (ISMS) is a collection of processes, documentation and operational artefacts (trackers, work instructions and service requests) that organisations use to manage information security. International standard, ISO 27001, is the most widely accepted security standard for information security management systems and includes a myriad of controls to manage the security of system change. The process for change, as identified by ISO 27001, is as follows:
Changes to any environment demand higher levels of risk/change management. The service management team must work closely with the information security team to successfully deploy modifications; particularly those emergency changes which often require shortcuts to the standard procedure to enable rapid implementation.
Irrespective of the nature of the change introduced, there should be a record of its provenance and reason for introduction; it needs to contain all the relevant approvals and documentation associated with its deployment. This audit record can, if necessary, assist in tracing problems associated with the change.
If businesses don’t have control of the change process and don’t monitor the introduction of application and system updates, it can lead to unexpected and therefore unplanned consequences, including security failures affecting information confidentiality, integrity and availability.
System and application event logs can be used to monitor systems and users. They become useful sources of information for monitoring the effect a change has on the business (be that positive or negative). From an information security perspective, the ISMS documents standard operating procedures (SOPs) for change introduction, along with SOPs for handling exceptions, faults and backouts. There are a variety of threats that the introduction of changes pose to businesses, so by auditing changes and correlating event logs against an appropriate threat model, changes that are harmful can be detected and fixed before any damage is done.
To monitor and report on the organisation’s security posture as changes are introduced, security teams need quality data from audit logs, including the following information:
Your security team can respond to changes that appear unusual or overly risky, especially if they adversely affect the organisation’s security posture. The use of system privileges or special administrative utilities that may be necessary to expedite an emergency change require particular attention; if they are not specified as required in the change’s documentation, they may be indicative of an attack (or at least worth investigating).
Your SOC team should assess any files accessed during the change process and record the system accounts used to install that change. If the change is anticipated to be installed by a user account, but it’s being installed by an administrator or system account, it’s time to investigate why this is so. It could be that the change is an attack.
Protecting your business from cyber-attackers requires your security team to assess and tune their security monitoring systems. A commonly used platform used by SOC teams is a Security Information and Event Management (SIEM) system; it helps security analysts determine which files have been accessed and report on the nature of that access. The SIEM records the IP addresses and network protocols used for the system change and reports on unusual behaviour requiring analyst follow up.
As your analysts develop familiarity with the business processes and better understand the nature of the change, they should use the correlation capabilities of their SIEM to assess the change against a threat model. If it looks unusual or suspicious, they can raise the alarm and begin the incident investigation.
The retrospective approach to developing SOC alarms works, and it’s been the mainstay of SOC activities for many years, but it is slow and protracted and manually intensive. Modern SIEMs collect all the vital information in seconds and even learn what “good” behaviour looks like; if anomalous activity is detected it is immediately alerted for analyst investigation.
Threat modelling is a process by which SOC teams model how an attacker might target and breach their systems. By collaborating with a penetration tester your analyst can shorten the time it takes to model attacks because they can mimic the attacker’s mindset and how they would introduce malware into your systems. To hack into your organisation, a penetration tester causes systems to react in the same way that they would if they were under a malicious attack. By emulating a hacker, your analysts can then develop rules in the SIEM that detect the kinds of tools, behaviours, protocols and malware signatures associated with those techniques.
To close the change process loop, your analysts can now search the service management tools for approvals for behaviours, and compare the actual filename, file version, or account name with the expected change to key attributes. If another rule, based on the threat model changes, triggers, as part of the process, even if some of the basic information looks right, the analyst can still start the investigation process as there are indicators of compromise that can’t be ignored.
<<< Part 2a: Australia’s Essential Eight: Beyond Endpoint Control <<< Part 2b: Activating UK NCSC & US NIST Guidelines: Beyond Endpoint Control Part 4: Systematic Measurement of Cyber Controls >>> As much as we invest into cyber security controls, external threats are inevitable. In a recent Notifiable Data Breaches Report from the Office of the […]Read more
Keen campers, scouts and even the Swiss Army know – that a good penknife is indispensable. This simple device has mitigated many a disaster at one point in time or another. Whether it’s to cut through a bit of string, tighten a screw or simply to solve the problem of no bottle opener in the […]Read more
Supply chain risk is an area of cyber security that demands the ongoing attention of every enterprise; because it can make the difference between being resilient or not. It’s no surprise that insurers warn that the vulnerability of supply chains is potentially a systemic risk that can quickly propagate across supply chain dominated industries. Organisations […]Read more
It took a “tripartite cyber assessment” by the Australian Prudential Regulation Authority (APRA) to identify that a sample of financial organisations had inadequate cyber security: poor security control management, a lack of business recovery planning and inadequate 3rd party risk assessment. Why were there gaps? Where is the failure? Clearly the common practice of unsubstantiated […]Read more
The discussion over data-driven vs qualitative cyber security assessment has been going for some time. Nowadays, it is at the top of the priority list for many security and senior executive teams. Managing cyber security has always been a noble ambition but without reliable measurement, the lack of actionable information makes evidence-based management decisions almost […]Read more
Attack Surface Management (ASM) characterises a business’s security risks as the monitoring and risk mitigation of a constantly changing and vulnerable “risk-surface”. Importantly, this attack surface extends to both internal and external assets and services. Some ASM solutions deliver clear visibility across both Internet facing and internal assets. Others do not. Instead, they assess external […]Read more
The UK Government has released its annual “Cyber Security Breaches Survey 2023”. It provides some valuable insights into how cyber security is currently being managed in the UK, by a range of organisations. It also speaks to how current competing economic priorities are impacting the effectiveness of some cyber security management efforts. The full report […]Read more
Solving the mismatch between cyber security reporting and directors’ requirements You are undoubtedly familiar with the headlines; you may have even become in part desensitised to them: ‘Cyber-attacks are increasingly damaging’, or ‘large amounts of personal data are most at risk’. The important take-away, however, is that modern day thieves can easily gain access to […]Read more
A system to address the untrustworthy security environment Zero trust approaches to security have been talked about for a while; but in recent times they have certainly gained more currency. As a model for protecting data and services, the simplicity of the concept is its biggest strength – assume, as a default position, there is […]Read more
The ongoing protection of Critical Infrastructure from cyber-attacks has implications for us all – whether it’s supporting our health, well-being or simply our way of life, there is good reason to reflect on the effectiveness your cyber security. Cyber security risks are nothing new and the vulnerability of critical infrastructure to them (and the heightened […]Read more
Read by directors, executives, and security professionals globally, operating in the most complex of security environments.