Blog
Dentro do SOC
Darktrace vs Cobalt Strike: Como Antigena interceptou e atrasou uma intrusão de Cobalt Strike






In December 2021 several CVEs[1] were issued for the Log4j vulnerabilities that sent security teams into a global panic. Threat actors are now continuously scanning external infrastructure for evidence of the vulnerability to deploy crypto-mining malware.[2] However, through December ‘21 – February ‘22, it was ransomware groups that seized the initiative.
Compromisso
Em janeiro de 2022, um cliente Darktrace deixou um servidor VMware de face externa desatrelaçado permitindo que o Cobalt Strike fosse instalado com sucesso. Vários IoCs indicam que os operadores da Cuba Ransomware estavam por trás do ataque. Graças ao serviço Darktrace SOC, o cliente foi notificado da ameaça ativa em sua rede, e a Resposta Autônoma de Antigena conseguiu manter os atacantes à distância antes de ocorrerem os eventos de criptografia.
Inicialmente o servidor VMware violou dois modelos relacionados a um download anômalo de scripts e um novo agente de usuário, ambos conectados via HTTP. Como referido em um blog anterior Darktrace , ambos os modelos haviam sido vistos em explorações anteriores do Log4j. Entretanto, como em todos os modelos Darktrace , o deck do modelo não foi projetado para detectar apenas uma exploração, variante de infecção, ou APT.

Figura 1: Darktrace modelos que quebram devido ao download do script malicioso
Investigação de analistas
Um PCAP do script baixado mostrou que ele continha um JavaScript fortemente ofuscado. Após uma investigação do OSINT, um script semelhante foi descoberto, o que provavelmente violou as mesmas regras de Yara.

Figura 2: PCAP do pedido inicial HTTP GET para o componente Windows Script

Figura 3: PCAP da resposta HTTP inicial contendo JavaScript ofuscado

Figure 4: A similar script that has been observed installing additional payloads after an initial infection[3]
Embora não seja uma correspondência exata, este código desobstruído compartilhou semelhanças com aqueles vistos ao baixar outros trojans bancários.
Tendo identificado na interface Darktrace que este era um servidor VMware, o analista isolou as conexões externas de entrada para o servidor pouco antes das solicitações HTTP GET e foi capaz de encontrar um endereço IP associado às tentativas de exploração do Log4j.

Figura 5: Logs de busca avançada mostrando conexões SSL recebidas a partir de um endereço IP ligado a explorações Log4j
Através da Pesquisa Avançada, o analista identificou picos pouco antes e imediatamente após o download. Isto sugeriu que os arquivos foram baixados e executados explorando a vulnerabilidade do Log4j.
Resposta de Antigena

Figura 6: AI Analyst revela tanto os downloads do script quanto o agente de usuário incomum associado às conexões

Figura 7: Antigena bloqueou todas as outras conexões a esses pontos finais após os downloads
Cobalt Strike
O Cobalt Strike é uma ferramenta popular para atores ameaçadores, pois pode ser usado para executar uma faixa de técnicas MITRE ATT&CK. Neste caso, o ator da ameaça tentou táticas de comando e controle para girar através da rede, no entanto, Antigena respondeu prontamente quando o malware tentou se comunicar com a infra-estrutura externa.
Na quarta-feira, 26 de janeiro, o beacon DNS tentou se conectar à infra-estrutura maliciosa. Antigena respondeu, e um analista do SOC Darktrace emitiu um alerta.

Figura 8: Darktrace detectou as solicitações DNS suspeitas e Antigena emitiu uma resposta
O atacante mudou sua estratégia mudando para um servidor diferente "bluetechsupply[.]com" e começou a emitir comandos sobre TLS. Novamente, Darktrace detectou estas conexões e o AI Analyst relatou o incidente (Figura 9, abaixo). Fontes da OSINT indicaram posteriormente que este destino é afiliado à Cobalt Strike e foi registrado apenas 14 dias antes deste incidente.

Figura 9: Resumo do analista de IA da atividade suspeita de balizamento
Simultaneamente a estas conexões, o dispositivo escaneou vários dispositivos internos através de uma varredura ICMP e depois escaneou o controlador de domínio sobre as principais portas TCP, incluindo 139 e 445 (SMB). Isto foi seguido por uma tentativa de escrever um arquivo executável para o controlador de domínio. Enquanto Antigena intervinha na gravação do arquivo, outro analista do SOC Darktrace estava emitindo um alerta devido ao aumento da atividade.

Figura 10: Resumo do arquivo .dll do analista de IA que Antigena interceptou no diretório Windows/temp do controlador de domínio
Após a última rodada de blocos de Antigena, o ator ameaçador tentou mudar os métodos novamente. O servidor VMware utilizou a Ferramenta de Acesso Remoto/Trojan NetSupport Manager em uma tentativa de instalar mais malware.

Figura 11: Darktrace revela a mudança de tática do atacante
Apesar desta escalada, Darktrace mais uma vez bloqueou a conexão.
Talvez devido a uma incapacidade de conexão com a infra-estrutura C2, o ataque parou em seus rastros por cerca de 12 horas. Graças à Antigena e à equipe SOC Darktrace , a equipe de segurança teve tempo para remediar e se recuperar da ameaça ativa em sua rede. Curiosamente, Darktrace detectou uma tentativa final de pivotar a partir da máquina, com uma incomum conexão PowerShell Win-RM a uma máquina interna. O protocolo Win-RM moderno normalmente utiliza a porta 5985 para conexões HTTP, entretanto, máquinas pré-Windows 7 podem usar o Windows 7 indicando que este servidor estava rodando um sistema operacional antigo.

Figura 12: Darktrace detecta o uso incomum do PowerShell
Cuba Ransomware
While no active encryption appears to have taken place for this customer, a range of IoCs were identified which indicated that the threat actor was the group being tracked as UNC2596, the operators of Cuba Ransomware.[4]
These IoCs include: one of the initially dropped files (komar2.ps1,[5] revealed by AI Analyst in Figure 6), use of the NetSupport RAT,[6] and Cobalt Strike beaconing.[7] These were implemented to maintain persistence and move laterally across the network.
As operadoras da Cuba Ransomware preferem exfiltrar dados para sua infra-estrutura de sinalização em vez de utilizar fornecedores de armazenamento em nuvem, porém não foi observada nenhuma evidência de atividade de upload na rede do cliente.
Pensamentos finais
Servidores VMware de face externa vulneráveis à exploração do Log4j estão sendo ativamente visados pelos atores da ameaça com o objetivo de detonação do resgate. Sem utilizar regras ou assinaturas, Darktrace foi capaz de detectar todas as etapas do compromisso. Enquanto Antigena atrasou o ataque, forçando o ator da ameaça a mudar os servidores C2 constantemente, a equipe de analistas do Darktrace retransmitiu suas descobertas à equipe de segurança que foi capaz de remediar as máquinas comprometidas e impedir a detonação de uma carga útil final de resgate.
For Darktrace customers who want to find out more about Cobalt Strike, refer here for an exclusive supplement to this blog.
Anexo
Darktrace detecções de modelos
Compromisso inicial:
- Dispositivo / Novo agente do usuário para servidor interno
- Anomalous Server Activity / Novo agente de usuário do sistema Internet Facing
- Experimento / Grande número de conexões suspeitas de sucesso
Quebras a partir de Dispositivos Críticos / DC:
- Dispositivo / Grande número de quebras de modelo
- Antigena / Rede / Ameaça Externa / Arquivo Antigena então Novo Bloco de Saída
- Dispositivo / SMB Lateral Movement
- Roteiro SMB Experimental / SMB Script Write Incomum V2
- Conformidade / Violação do modelo de conformidade de alta prioridade
- Atividade anômala do servidor / atividade externa anômala do dispositivo de Rede Crítica
- Experimental / Possível Cobalt Strike Server IP V2
Movimento Lateral:
- Antigena / Rede / Ameaça interna / Antigena Atividade Interna de Arquivo Anomaloso
- Conformidade / SMB Drive Write
- Arquivo anômalo / Interno / Executável Carregado para DC
- Experimento / Grande número de conexões com falhas suspeitas
- Compromisso / Comportamento de balizamento suspeito
- Antigena / Rede / Anomalia Significativa / Antigena Quebra de Bloco ao Longo do Tempo
- Antigena / Rede / Ameaça externa / Antigena bloco de atividade suspeita
- Conexão Anômala / Alto Volume de Conexões com Domínio Raro
- Antigena / Rede / Anomalia Significativa / Antigena Monitoramento Avançado a partir do Bloco do Servidor
Atividade de varredura em rede:
- Dispositivo / Atividade de escaneamento de SMBs suspeitas
- Experimental / Network Scan V2
- Digitalização de endereço do dispositivo / ICMP
- Atividade de escaneamento experimental / Possível SMB
- Atividade de Escaneamento Experimental / Possível SMB V2
- Antigena / Rede / Ameaça interna / Antigena Network Scan Block
- Digitalização do dispositivo / rede
- Compromisso / DNS / Possível DNS Beacon
- Dispositivo / Dispositivo de Faceamento de Internet com Alerta de Alta Prioridade
- Antigena / Rede / Anomalia Significativa / Antigena Monitoramento Avançado a partir do Bloco do Servidor
DNS / Atividade de Cobalt Strike
- Experimental / Possível Cobalt Strike Server IP
- Experimental / Possível Cobalt Strike Server IP V2
- Antigena / Rede / Ameaça Externa / Arquivo Antigena então Novo Bloco de Saída
- Antigena / Rede / Ameaça Externa / Antigena Bloco de Arquivos Suspeitos
- Conexão anômala / Novo agente de usuário para IP sem nome de host
- Arquivo Anomalous / Script de Localização Externa Rara
MITRE ATT&CK técnicas observadas

Indicators of Compromise

Obrigado a Brianna Leddy, Sam Lister e Marco Alanis por suas contribuições.
Footnotes
1.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44530
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
2. https://www.toolbox.com/it-security/threat-reports/news/log4j-vulnerabilities-exploitation-attempts
3. https://twitter.com/ItsReallyNick/status/899845845906071553
4. https://www.mandiant.com/resources/unc2596-cuba-ransomware
5. https://www.ic3.gov/Media/News/2021/211203-2.pdf
6. https://threatpost.com/microsoft-exchange-exploited-cuba-ransomware/178665/
7. https://www.bleepingcomputer.com/news/security/microsoft-exchange-servers-hacked-to-deploy-cuba-ransomware/
8. https://gist.github.com/blotus/f87ed46718bfdc634c9081110d243166
Curtiu e quer mais?
More in this series
Blog
Dentro do SOC
Protecting Prospects: How Darktrace Detected an Account Hijack Within Days of Deployment



Cloud Migration Expanding the Attack Surface
Cloud migration is here to stay – accelerated by pandemic lockdowns, there has been an ongoing increase in the use of public cloud services, and Gartner has forecasted worldwide public cloud spending to grow around 20%, or by almost USD 600 billion [1], in 2023. With more and more organizations utilizing cloud services and moving their operations to the cloud, there has also been a corresponding shift in malicious activity targeting cloud-based software and services, including Microsoft 365, a prominent and oft-used Software-as-a-Service (SaaS).
With the adoption and implementation of more SaaS products, the overall attack surface of an organization increases – this gives malicious actors additional opportunities to exploit and compromise a network, necessitating proper controls to be in place. This increased attack surface can leave organization’s open to cyber risks like cloud misconfigurations, supply chain attacks and zero-day vulnerabilities [2]. In order to achieve full visibility over cloud activity and prevent SaaS compromise, it is paramount for security teams to deploy sophisticated security measures that are able to learn an organization’s SaaS environment and detect suspicious activity at the earliest stage.
Darktrace Immediately Detects Hijacked Account
In May 2023, Darktrace observed a chain of suspicious SaaS activity on the network of a customer who was about to begin their trial of Darktrace/Cloud™ and Darktrace/Email™. Despite being deployed on the network for less than a week, Darktrace DETECT™ recognized that the legitimate SaaS account, belonging to an executive at the organization, had been hijacked. Darktrace/Email was able to provide full visibility over inbound and outbound mail and identified that the compromised account was subsequently used to launch an internal spear-phishing campaign.
If Darktrace RESPOND™ were enabled in autonomous response mode at the time of this compromise, it would have been able to take swift preventative action to disrupt the account compromise and prevent the ensuing phishing attack.
Account Hijack Attack Overview
Unusual External Sources for SaaS Credentials
On May 9, 2023, Darktrace DETECT/Cloud detected the first in a series of anomalous activities performed by a Microsoft 365 user account that was indicative of compromise, namely a failed login from an external IP address located in Virginia.

Just a few minutes later, Darktrace observed the same user credential being used to successfully login from the same unusual IP address, with multi-factor authentication (MFA) requirements satisfied.

A few hours after this, the user credential was once again used to login from a different city in the state of Virginia, with MFA requirements successfully met again. Around the time of this activity, the SaaS user account was also observed previewing various business-related files hosted on Microsoft SharePoint, behavior that, taken in isolation, did not appear to be out of the ordinary and could have represented legitimate activity.
The following day, May 10, however, there were additional login attempts observed from two different states within the US, namely Texas and Florida. Darktrace understood that this activity was extremely suspicious, as it was highly improbable that the legitimate user would be able to travel over 2,500 miles in such a short period of time. Both login attempts were successful and passed MFA requirements, suggesting that the malicious actor was employing techniques to bypass MFA. Such MFA bypass techniques could include inserting malicious infrastructure between the user and the application and intercepting user credentials and tokens, or by compromising browser cookies to bypass authentication controls [3]. There have also been high-profile cases in the recent years of legitimate users mistakenly (and perhaps even instinctively) accepting MFA prompts on their token or mobile device, believing it to be a legitimate process despite not having performed the login themselves.
New Email Rule
On the evening of May 10, following the successful logins from multiple US states, Darktrace observed the Microsoft 365 user creating a new inbox rule, named “.’, in Microsoft Outlook from an IP located in Florida. Threat actors are often observed naming new email rules with single characters, likely to evade detection, but also for the sake of expediency so as to not expend any additional time creating meaningful labels.
In this case the newly created email rules included several suspicious properties, including ‘AlwaysDeleteOutlookRulesBlob’, ‘StopProcessingRules’ and “MoveToFolder”.
Firstly, ‘AlwaysDeleteOutlookRulesBlob’ suppresses or hides warning messages that typically appear if modifications to email rules are made [4]. In this case, it is likely the malicious actor was attempting to implement this property to obfuscate the creation of new email rules.
The ‘StopProcessingRules’ rule meant that any subsequent email rules created by the legitimate user would be overridden by the email rule created by the malicious actor [5]. Finally, the implementation of “MoveToFolder” would allow the malicious actor to automatically move all outgoing emails from the “Sent” folder to the “Deleted Items” folder, for example, further obfuscating their malicious activities [6]. The utilization of these email rule properties is frequently observed during account hijackings as it allows attackers to delete and/or forward key emails, delete evidence of exploitation and launch phishing campaigns [7].
In this incident, the new email rule would likely have enabled the malicious actor to evade the detection of traditional security measures and achieve greater persistence using the Microsoft 365 account.

Account Update
A few hours after the creation of the new email rule, Darktrace observed the threat actor successfully changing the Microsoft 365 user’s account password, this time from a new IP address in Texas. As a result of this action, the attacker would have locked out the legitimate user, effectively gaining full access over the SaaS account.

Phishing Emails
The compromised SaaS account was then observed sending a high volume of suspicious emails to both internal and external email addresses. Darktrace was able to identify that the emails attempting to impersonate the legitimate service DocuSign and contained a malicious link prompting users to click on the text “Review Document”. Upon clicking this link, users would be redirected to a site hosted on Adobe Express, namely hxxps://express.adobe[.]com/page/A9ZKVObdXhN4p/.
Adobe Express is a free service that allows users to create web pages which can be hosted and shared publicly; it is likely that the threat actor here leveraged the service to use in their phishing campaign. When clicked, such links could result in a device unwittingly downloading malware hosted on the site, or direct unsuspecting users to a spoofed login page attempting to harvest user credentials by imitating legitimate companies like Microsoft.

The malicious site hosted on Adobe Express was subsequently taken down by Adobe, possibly in response to user reports of maliciousness. Unfortunately though, platforms like this that offer free webhosting services can easily and repeatedly be abused by malicious actors. Simply by creating new pages hosted on different IP addresses, actors are able to continue to carry out such phishing attacks against unsuspecting users.
In addition to the suspicious SaaS and email activity that took place between May 9 and May 10, Darktrace/Email also detected the compromised account sending and receiving suspicious emails starting on May 4, just two days after Darktrace’s initial deployment on the customer’s environment. It is probable that the SaaS account was compromised around this time, or even prior to Darktrace’s deployment on May 2, likely via a phishing and credential harvesting campaign similar to the one detailed above.

Darktrace Coverage
As the customer was soon to begin their trial period, Darktrace RESPOND was set in “human confirmation” mode, meaning that any preventative RESPOND actions required manual application by the customer’s security team.
If Darktrace RESPOND had been enabled in autonomous response mode during this incident, it would have taken swift mitigative action by logging the suspicious user out of the SaaS account and disabling the account for a defined period of time, in doing so disrupting the attack at the earliest possible stage and giving the customer the necessary time to perform remediation steps. As it was, however, these RESPOND actions were suggested to the customer’s security team for them to manually apply.

Nevertheless, with Darktrace DETECT/Cloud in place, visibility over the anomalous cloud-based activities was significantly increased, enabling the swift identification of the chain of suspicious activities involved in this compromise.
In this case, the prospective customer reached out to Darktrace directly through the Ask the Expert (ATE) service. Darktrace’s expert analyst team then conducted a timely and comprehensive investigation into the suspicious activity surrounding this SaaS compromise, and shared these findings with the customer’s security team.
Conclusão
Ultimately, this example of SaaS account compromise highlights Darktrace’s unique ability to learn an organization’s digital environment and recognize activity that is deemed to be unexpected, within a matter of days.
Due to the lack of obvious or known indicators of compromise (IoCs) associated with the malicious activity in this incident, this account hijack would likely have gone unnoticed by traditional security tools that rely on a rules and signatures-based approach to threat detection. However, Darktrace’s Self-Learning AI enables it to detect the subtle deviations in a device’s behavior that could be indicative of an ongoing compromise.
Despite being newly deployed on a prospective customer’s network, Darktrace DETECT was able to identify unusual login attempts from geographically improbable locations, suspicious email rule updates, password changes, as well as the subsequent mounting of a phishing campaign, all before the customer’s trial of Darktrace had even begun.
When enabled in autonomous response mode, Darktrace RESPOND would be able to take swift preventative action against such activity as soon as it is detected, effectively shutting down the compromise and mitigating any subsequent phishing attacks.
With the full deployment of Darktrace’s suite of products, including Darktrace/Cloud and Darktrace/Email, customers can rest assured their critical data and systems are protected, even in the case of hybrid and multi-cloud environments.
Credit: Samuel Wee, Senior Analyst Consultant & Model Developer
Appendices
References
[2] https://www.upguard.com/blog/saas-security-risks
[4] https://learn.microsoft.com/en-us/powershell/module/exchange/disable-inboxrule?view=exchange-ps
[7] https://blog.knowbe4.com/check-your-email-rules-for-maliciousness
Darktrace Model Detections
Darktrace DETECT/Cloud and RESPOND Models Breached:
SaaS / Access / Unusual External Source for SaaS Credential Use
SaaS / Unusual Activity / Multiple Unusual External Sources for SaaS Credential
Antigena / SaaS / Antigena Unusual Activity Block (RESPOND Model)
SaaS / Compliance / New Email Rule
Antigena / SaaS / Antigena Significant Compliance Activity Block
SaaS / Compromise / Unusual Login and New Email Rule (Enhanced Monitoring Model)
Antigena / SaaS / Antigena Suspicious SaaS Activity Block (RESPOND Model)
SaaS / Compromise / SaaS Anomaly Following Anomalous Login (Enhanced Monitoring Model)
SaaS / Compromise / Unusual Login and Account Update
Antigena / SaaS / Antigena Suspicious SaaS Activity Block (RESPOND Model)
IoC – Type – Description & Confidence
hxxps://express.adobe[.]com/page/A9ZKVObdXhN4p/ - Domain – Probable Phishing Page (Now Defunct)
37.19.221[.]142 – IP Address – Unusual Login Source
35.174.4[.]92 – IP Address – Unusual Login Source
MITRE ATT&CK Mapping
Tactic - Techniques
INITIAL ACCESS, PRIVILEGE ESCALATION, DEFENSE EVASION, PERSISTENCE
T1078.004 – Cloud Accounts
DISCOVERY
T1538 – Cloud Service Dashboards
CREDENTIAL ACCESS
T1539 – Steal Web Session Cookie
RESOURCE DEVELOPMENT
T1586 – Compromise Accounts
PERSISTENCE
T1137.005 – Outlook Rules

Blog
Darktrace/Email in Action: Why AI-Driven Email Security is the Best Defense Against Sustained Phishing Campaigns
_11zon.jpg)


Stopping the bad while allowing the good
Since its inception, email has been regarded as one of the most important tools for businesses, revolutionizing communication and allowing global teams to become even more connected. But besides organizations heavily relying on email for their daily operations, threat actors have also recognized that the inbox is one of the easiest ways to establish an initial foothold on the network.
Today, not only are phishing campaigns and social engineering attacks becoming more prevalent, but the level of sophistication of these attacks are also increasing with the help of generative AI tools that allow for the creation of hyper-realistic emails with minimal errors, effectively lowering the barrier to entry for threat actors. These diverse and stealthy types of attacks evade traditional email security tools based on rules and signatures, because they are less likely to contain the low-sophistication markers of a typical phishing attack.
In a situation where the sky is the limit for attackers and security teams are lean, how can teams equip themselves to tackle these threats? How can they accurately detect increasingly realistic malicious emails and neutralize these threats before it is too late? And importantly, how can email security block these threats while allowing legitimate emails to flow freely?
Instead of relying on past attack data, Darktrace’s Self-Learning AI detects the slightest deviation from a user’s pattern of life and responds autonomously to contain potential threats, stopping novel attacks in their tracks before damage is caused. It doesn’t define ‘good’ and ‘bad’ like traditional email tools, rather it understands each user and what is normal for them – and what’s not.
This blog outlines how Darktrace/Email™ used its understanding of ‘normal’ to accurately detect and respond to a sustained phishing campaign targeting a real-life company.
Responding to a sustained phishing attack
Over the course of 24 hours, Darktrace detected multiple emails containing different subjects, all from different senders to different recipients in one organization. These emails were sent from different IP addresses, but all came from the same autonomous system number (ASN).

The emails themselves had many suspicious indicators. All senders had no prior association with the recipient, and the emails generated a high general inducement score. This score is generated by structural and non-specific content analysis of the email – a high score indicates that the email is trying to induce the recipient into taking a particular action, which may lead to account compromise.
Additionally, each email contained a visually prominent link to a file storage service, hidden behind a shortened bit.ly link. The similarities across all these emails pointed to a sustained campaign targeting the organization by a single threat actor.


With all these suspicious indicators, many models were breached. This drove up the anomaly score, causing Darktrace/Email to hold all suspicious emails from the recipients’ inboxes, safeguarding the recipients from potential account compromise and disallowing the threats from taking hold in the network.
Imagining a phishing attack without Darktrace/Email
So what could have happened if Darktrace had not withheld these emails, and the recipients had clicked on the links? File storage sites have a wide variety of uses that allow attackers to be creative in their attack strategy. If the user had clicked on the shortened link, the possible consequences are numerous. The link could have led to a login page for unsuspecting victims to input their credentials, or it could have hosted malware that would automatically download if the link was clicked. With the compromised credentials, threat actors could even bypass MFA, change email rules, or gain privileged access to a network. The downloaded malware might also be a keylogger, leading to cryptojacking, or could open a back door for threat actors to return to at a later time.


The limits of traditional email security tools
Secure email gateways (SEGs) and static AI security tools may have found it challenging to detect this phishing campaign as malicious. While Darktrace was able to correlate these emails to determine that a sustained phishing campaign was taking place, the pattern among these emails is far too generic for specific rules as set in traditional security tools. If we take the characteristic of the freemail account sender as an example, setting a rule to block all emails from freemail accounts may lead to more legitimate emails being withheld, since these addresses have a variety of uses.
With these factors in mind, these emails could have easily slipped through traditional security filters and led to a devastating impact on the organization.
Conclusão
As threat actors step up their attacks in sophistication, prioritizing email security is more crucial than ever to preserving a safe digital environment. In response to these challenges, Darktrace/Email offers a set-and-forget solution that continuously learns and adapts to changes in the organization.
Through an evolving understanding of every environment in which it is deployed, its threat response becomes increasingly precise in neutralizing only the bad, while allowing the good – delivering email security that doesn’t come at the expense of business growth.