Exabeam details how South Australian public sector attack could have been stopped in its tracks

It has been widely reported recently that South Australian government employees have been the victims of a cyberattack, with personal data stolen as the result of malicious activity on payroll software provider Frontier. A further 13,000 employees were added to the 80,000 announced in late 2021, bringing the total to well over 90,000 current and former employees whose personal credentials were compromised in the attack.

 

Exabeam’s Sales Director for APJ, Gareth Cox, reminds organisations that an organisation “can’t defend what it can’t see”, and suggests several strategies that would have made such an attack much harder to perpetrate, or discovered the breach before so many employees were compromised.

 

Advertisement

“As our President Ralph Pisani wrote recently, there are three main questions regarding their security operations that every CISO needs to answer. While no silver bullets exist, Ralph goes on to explain that systems exist, whether they are built or bought, that will allow defenders who address these three questions to win, in situations like the one experienced in south Australia.”

 

 

What every CISO must answer to enable a best-in-class security operations program.

Ralph Pisani, President, Exabeam

 

  1. Do you know what normal looks like for every user and entity in your environment?

This is the million-dollar question. Having a handle on what normal activity looks like in your environment is key to detecting anomalous activity.

 

Some examples:

 

A user is resetting their credentials outside of the corporate change window.

A user who doesn’t usually create new accounts has created several new accounts outside of the provisioning process.

A contractor accessed a new system using admin credentials.

A system in your cloud account is accessing a database every 30 seconds.

A user has staged some files and has not done anything else.

A system is communicating with a remote server we’ve never seen.

A user is copying a significantly large number of files.

A developer is accessing a system with backdoor access.

A user just sent a large number of emails to their personal account.

A previously quiet service account is now surfing the internet or signing in interactively to other systems.

With behavioural models running in the background, you enable a CPU, rather than one of your heroes, to spot anomalies and assign risk values. Rules are great but only detect known knowns. There’s a little more to this process; one anomaly typically isn’t enough to take decisive action. That sets us up for the next question.

 

  1. Do you create and use timelines?

I hope that you have never experienced a breach. If you have, one of the first things the expensive third party you hire is going to do is build a timeline of activities to help pinpoint the attack and the impacted systems — even at its best, this is still static and point-in-time. I’ve been in cybersecurity for more than 25 years, and I’ve yet to see anything more powerful than the impact of timelines for a security operations team. When done correctly, timelines answer the unanswerable; they provide a contextualized time window of any activity associated with a user or asset. If any one of the above examples is triggered, the risk score is elevated and each user or asset can automatically be placed on a watchlist. The timeline is ready to help any level of analyst determine what other activities have occurred that might raise their risk level and drive automated or manual intervention.

 

If you experience a breach, you likely will end up paying a third-party IR firm to help you assess the damage and toss out adversaries. The tool they use to do it is a timeline. What if there were an easier and better way to leverage timelines? How about an automatic way? Exabeam Smart TimelinesTM are an evolution beyond third-party support because, among other things, they are automated and identify abnormal behaviour. Timelines are showstoppers — attackers hate them!

 

  1. What’s your plan for credential-based attacks?

With few exceptions, all of the most recent destructive breaches have been from insiders and credential-based attacks. The adversaries know the drill: acquire someone’s credentials, avoid external threat detection, gain access using legitimate credentials, and move laterally. With credentials on sale in criminal marketplaces for $15 a person, and admin credentials selling for anywhere from $500 to $100,000 each, there’s an opportunity for both sellers and buyers. Add to this, the recent Lapsus$ attacks present a new wrinkle, where the attacking/criminal organization is using social media to recruit insiders for tens of thousands of dollars. We see this as a new Insider Threat vector, “Colluding Insiders”.

 

There’s more. Your credential-based attack plan must reach beyond cybercriminals. You need to account for others: employees, contractors, vendors, partners, and ex-employees whose access has not been disabled. This level of attention supports supply chain and third-party risk management security as well.

 

Your plan should be to identify credential-based attacks (aka insider threats) as quickly as possible before they become major incidents. Unlike external threats, insider threats typically evolve over a long period of time. To discover them, you have to be able to monitor user behaviour that isn’t within a normal range (question #1) and likely incorporates timelines (question #2) to respond immediately.

 

Simply put, best-in-class security operations need the well-thought-out capabilities of a next-gen SIEM.

 

Organise security operations around capabilities

The key tool to identifying insider threat behaviour is a SIEM with UEBA capabilities that apply data science across all users and asset activities to determine a normal baseline of expected behaviour. Then, when behaviour drifts away from that baseline, the solution brings those users and/or assets to the attention of security analysts.