Author: Robert Broxup

Analysis of notes and emails showed that among readers’ feedback and questions, the following eight were the most prominent risk areas and included both current mitigation activity and activity planned for over the foreseeable future.

• Infected media

• Legal Implications of data in the cloud

• Privileged Access

• Separation of live and development systems

• Security patching

• Are publicised risks genuine or politically motivated

• Tailgating

• CEO impersonation fraud

Some of our readers reported that they were more concerned about other threats than any specific cyber threat. These areas included:

• Terrorism

• Excessive Regulation

• Increasing Taxation

• Climate Change

Essential Software Asset Management (SAM) points include:

• Maintain an accurate inventory of authorised software. Knowing what is allowed makes identifying and removing unauthorised software installations more manageable.

• Ensure that all your software is correctly licensed. Avoid unnecessary purchasing of software licences by limiting usage based on job roles. Reconcile software purchases with software usage.

• Maintain control over who can install software packages. Avoid ad hoc software installations and proliferation to reduce licence exposure and cyber threats.

• Ensure that authorised software is up to date and supported by vendors. Reduce exploitable software vulnerabilities.

• Segregate business-critical software from other lower priority systems. Avoid less important systems from impacting the business.

• Keep control of software support costs. Accurate information about software usage contributes to avoiding excessively priced support contracts.

• Choose the right product to fit your business environment. Ensure the solution works with existing platforms and operating systems, and the software works out of the box or with minimum configuration. Avoid the trap of buying software and then paying expensive project and development costs to make it fit for purpose.

Storing login credentials within 3^rd party apps can introduce significant security risks. I recently tested an application to determine its usefulness and fitness for purpose. As with several other applications experimented with over the years, this one included the option to integrate directly with other systems; in this case, one of the social media platforms. In the settings, a configuration option was available to add the user name and password so that the application could connect to access data directly. A couple of examples include:

• Banking applications which allow connections to several bank accounts where data is collected from multiple sources to create a financial dashboard

• Apps that connect to file storage systems, such as to catalogue songs and create playlists

These tools offer useful functionality, but there are security implications with this concept. Firstly, let’s not confuse this with single-sign-on (SSO) capability. Many websites and applications integrate with Facebook and Google for login purposes, but when signing in with Facebook or Google, the apps don’t have direct access to the login credentials. The quantity of data shared through this process has been controversial and has drawn vast media attention.  However, the focus here is on cases where applications ask for login credentials to be entered and stored for subsequent use, and where the application has direct access to the credentials. Essentially, this is permitting the application to access other systems and by extension, consequently, potentially giving human access to those systems.

How do you know what these applications are going to do with your login credentials? The logon credentials could be stored securely, but could just as easily find themselves held in plain text in a database with little or no security. Applications can easily be custom made to offer something useful to the target audience, with the hidden agenda of capturing user credentials given willingly by their users.

Banking organisations and social media platforms invent significant resources to improve security. It doesn’t make sense to use them with apps that may have been developed by a small business or one person with minimal resources and information security capability.

Here are some options to reduce the risks:

• Don’t give 3^rd party user credentials to apps, websites or other services

• Exercise vendor and application due diligence before adding 3^rd party user credentials

• If 3^rd party application integration is essential, consider creating a dedicated account to use. Depending on the purpose, this may or may not be a viable option.

It is best practice never to share your username and password with anyone. Sharing your usernames and passwords with 3^rd party applications can have the same or worse consequences.

There are several ways in which risks can be dealt with, depending on the circumstances and individual or corporate risk appetite.

• Severity – the consequences of an event taking place

• Probability – the likelihood of an event taking place

• Risk = severity x probability – high probability and high severity equate to a high-risk

It is also important to note the difference between Perceived Risk and Actual Risk:

• Actual risk – quantifiable and based on objective data, for example, according to the Department of Transport, there were 1784 deaths, 25,511 serious injuries and 160,597 casualties of all severities from road traffic accidents in the United Kingdom in 2018. Media coverage was low.

• Perceived risk – determined by individual perception and influenced by other factors such as news headlines, for example, Dutch aviation consulting firm To70 reported on 534 deaths in 2018 from passenger airline crashes. Almost every aeroplane crash becomes headline news, even in cases where there are no fatalities.

The perceived risk is that it is more dangerous to travel by passenger jet than to travel by car. However, the reverse is true when considering the actual risk. Statistically, it is far more dangerous to travel by car. A similar analysis shows that parachuting is statistically safer than crossing the road, whereas individual perception of the idea of jumping from a plane tells a different story.

The distinction is essential when it comes to managing risk to ensure that actions and investment are proportionate to the risk. Individuals and organisations often need to prioritise risks due to availability of resources, and consequently, investment in a perceived risk over dealing with an actual risk can be catastrophic. The reverse is also true. In cases where perceived risk influences a consumer’s decision to buy, a company can suffer substantial financial losses even if the actual risk is minuscule.

• Risk Avoidance

• Risk Mitigation

• Risk Acceptance

• Risk Transfer

Risk Avoidance

Risk avoidance is about implementing alternative plans and solutions to circumnavigate the events which carry risk. With no possibility of an event taking place, it doesn’t matter how severe the consequences are because, in the ‘Severity x Probability’ formula, the risk becomes ZERO. It is, of course, possible that implementing alternatives may introduce different risks which need assessment, but that is another story.

Risk Acceptance

Risk acceptance is about accepting that the event will, at some point, take place, and accepting responsibility for the consequences when it does take place. The ‘Severity x Probability’ will help determine the appropriateness of accepting the risk. It is also necessary to consider:

• The legality of accepting the risk

• Does the person accepting the risk have the authority to do so?

• Is the cost of risk mitigation proportionate to risk?

• Is it sensible to accept the risk?

Businesses accept risks for all sorts of reasons, including:

• Too expensive compared to the benefit

• Insufficient finance to mitigate the risk

• Insufficient human resources or skills to mitigate the risk

• Mitigating the risk is a lower priority than other risks

• Plans in place to mitigate risks at a later date

Keeping evidence of risk analysis along with conclusions reached and decisions made is essential.

Risk Mitigation

Risk Mitigation is about:

• Reducing the probability of an event taking place

• Reducing the severity of an event when it does take place

The cost of mitigation should be proportionate to the risk of not taking action.

Risk Transfer

Risk Transfer is the reduction of risk by transferring it someone else or to another company:

• An insurance policy – taking out an insurance policy essentially transfers some of the risks to the insurance company; how much depends on the insurance policy terms and conditions

• Project Contractual Terms – engaging with 3^rd parties to deliver projects or run services often includes terms and conditions of business which transfer risk from one party to another.

Only consider the transfer of risk if the party taking on the risk has the opportunity or means to reasonably reduce the risk, either on an ongoing basis or through adequate evaluation ahead of transferring risk.

Risk Transfer is essentially about paying someone else to take the risk, so it is crucial to make sure that the 3^rd party can accept the risk, and for the 3^rd party to receive sufficient reward to justify acceptance of the risk.