Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Truebot Malware: SafeBreach Coverage for US-CERT Alert (AA23-187A)

On July 6th, the Cybersecurity and Infrastructure Security Agency (CISA), the Federal Bureau of Investigation (FBI), the Multi-State Information Sharing and Analysis Center (MS-ISAC), and the Canadian Centre for Cyber Security (CCCS) released an advisory highlighting the newly identifying Truebot malware variants. Truebot (also known as Silence Downloader) is a botnet that has been used by the CL0P ransomware gang to collect and exfiltrate stolen target victim information.

Unlocking the Potential of UEBA With Logsign

In today's cybersecurity landscape, traditional security tools alone are inadequate in protecting organizations from advanced threats like data breaches, insider risks, and more. To effectively address these challenges, organizations require a comprehensive solution with UEBA (user and entity behavior analytics) capabilities. Let's discover the benefits of UEBA, and the unparalleled impact Logsign’s Unified Security Operations Platform has on UEBA.

See it in action: Privacy-first generative AI with Elastic

Get a look at the power of Elasticsearch and generative AI (GAI) in action — always putting privacy first and safeguarding your proprietary data. Several examples show off the art of the possible, with intuitive, personalized results you can’t achieve with just publicly available data.

Peeping Through Windows (Logs): Using Sysmon & Event Codes for Threat Hunting

If you have been reading our hunting series, you may have noticed that many threat hunting techniques center on network-centric data sources. Thus far, we have yet to speak about the big kahuna in our hunting tool chest. We are rectifying that right here, right now: we are going to talk about Microsoft Sysmon! In this article, we’re looking at using Sysmon to hunt for threats in endpoints.We’ll highlight some of the most valuable places to start hunting in your Windows logs.

FIPS 140-2: Validation VS Compliance

NIST established the crucial set of guidelines known as FIPS 140-2 to safeguard sensitive data, particularly for governmental organizations. It is to provide security and privacy when encrypting and decrypting data. The primary distinction between FIPS 140-2 validation and compliance is that. In contrast, validation involves determining if a system or product has been developed to comply with the standard’s requirements; compliance is putting those requirements into practice.

Why SOC 2 is an Industry Standard

SOC 2 (Service Organization Control 2) provides a framework for assessing and reporting on the security, availability, processing integrity, confidentiality, and privacy of systems and data of service organizations. It was developed by the American Institute of Certified Public Accountants (AICPA) to address the need for consistent and comprehensive security and privacy controls in service organizations.

Privileged Access Management (PAM) with Netwrix Solutions

Minimize your attack surface by eliminating the need for standing privilege altogether. Reduce the risk of business disruptions or compliance failures by managing and tracking all privileged activity in one place. Every day, organizations face the threat of cyberattacks that target privileged accounts. In fact, a staggering 74% of data breaches start with compromised privileged accounts and credentials. Is your organization prepared to defend against these attacks?