{"id":3503,"date":"2024-03-07T11:48:09","date_gmt":"2024-03-07T10:48:09","guid":{"rendered":"https:\/\/laokoon-security.com\/?page_id=3503"},"modified":"2024-11-29T12:14:20","modified_gmt":"2024-11-29T11:14:20","slug":"assume-breach","status":"publish","type":"page","link":"https:\/\/laokoon-security.com\/en\/service\/assume-breach\/","title":{"rendered":"Assume Breach"},"content":{"rendered":"
\n
\n
\n
\n

Assume Breach<\/strong><\/p>\n\n\n\n

Assume that you are being hacked!<\/h1>\n\n\n\n
\n
Configure Assume Breach<\/a><\/div>\n\n\n\n
Get advice<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\"Assume<\/figure>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n

Do you recognise the spread in your network?<\/h2>\n<\/div>\n\n\n\n

Assume Breach is a security strategy that assumes that an attack on a system or organisation is inevitable and that it is therefore important to minimise the impact of such an attack as much as possible. The idea behind Assume Breach is that it is better to prepare for the defence of attacks rather than assuming that a system is completely secure.<\/p>\n\n\n\n

\n

What measures does Assume Breach include?<\/h2>\n\n\n\n

When carrying out an Assume Breach Assessment, hackers proceed in a similar way to a Red Teaming Assessment.<\/p>\n\n\n\n

In contrast to red teaming, however, the attackers already have initial access to the internal network, for example via a compromised VPN access or malware that is executed on a computer.<\/p>\n\n\n\n

The basic idea is this: Just because a network appears secure at the current time, there is still a high probability that attackers will be able to gain initial access in one way or another.<\/p>\n\n\n\n

What is the aim of Assume Breach?<\/h2>\n\n\n\n

The aim of an Assume Breach Assessment is to analyse in a targeted manner whether an attacker attempting to spread within the internal network is detected and effective measures are taken to prevent further spread and the outflow of data.<\/p>\n<\/div>\n\n\n\n

Typical sequence of events in a real attack on a company<\/h2>\n\n\n\n
\n
\n
\n
<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n\n
\n
\n
An attacker gains initial access to the company<\/h6>\n\n\n\n

An employee uses the same password in several places. A social network to which the employee has logged in with the company email address suffers a data leak, as a result of which the employee's password becomes known. A hacker group exploits this and gains access to the internal network via the company's VPN.<\/p>\n<\/div>\n\n\n\n

\n
No alarms!<\/h6>\n\n\n\n

As the employee regularly dials in himself via the VPN, the behaviour of the attackers has not yet been conspicuous. They gain access to a host on which the employee has user rights and can access different network shares.<\/p>\n<\/div>\n\n\n\n

\n
Escalation of privileges!<\/h6>\n\n\n\n

The hackers can escalate their rights on the host and become the local administrator. This enables the attackers to download additional malware undetected and obtain further passwords and authorisation tokens.<\/p>\n<\/div>\n\n\n\n

\n
Spreading in the network<\/h6>\n\n\n\n

The additional user information and authorisation tokens allow the attackers to spread further and further across the network undetected. They use not only hacker tools, but also programs available on the systems that are not recognised as malicious by any anti-virus programs.<\/p>\n<\/div>\n\n\n\n

\n
Access to the heart of the company<\/h6>\n\n\n\n

By chaining rights escalations, the attackers gain access to the domain controller and thus control over all roles and rights assignments. Access to the backup server can now also take place undisturbed. The attackers have taken over the company and are starting to extract data.<\/p>\n<\/div>\n\n\n\n

\n
ENCRYPTION!<\/h6>\n\n\n\n

After large amounts of data containing sensitive internal company information have leaked out of the company, the hackers strike and encrypt all the files on the company's computers. They demand a large sum in cryptocurrencies before the decryption key is revealed.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\"\"<\/figure>\n\n\n\n

We thought we were in an excellent position with our endpoint protection and our managed SOC provider. Laokoon Security showed us where our blind spots were - and offered us targeted suggestions on how to eliminate them.<\/p>\n\n\n\n

CISO of a medium-sized company
<\/em>Assume Breach<\/strong><\/span><\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
When does an Assume Breach Assessment make sense for my company?<\/h6>\n\n\n\n