Operations | Monitoring | ITSM | DevOps | Cloud

At Cribl, we’ve been deeply investing in the Microsft Azure security space. Last year, we introduced a native integration with Microsoft Sentinel, enabling us to write data seamlessly to native and custom tables. As highlighted earlier, working with Microsoft Sentinel and Log Analytics involves interacting with tables with predefined column names and data types.

Organizations are rapidly adopting endpoint detection and response software to address the challenge and strengthen their overall network infrastructure security. Why? In large part because endpoints are used by the weakest link in the cybersecurity chain (humans!) and therefore create business risk. Endpoint devices typically have internet access, can reach sensitive internal data, and are primarily used by people who aren’t cybersecurity professionals.

Are you finding it challenging to control and secure the mobile devices used by your employees? The solution may lie in a deeper understanding of Mobile Device Management (MDM), particularly the difference between supervised and unsupervised devices. This seemingly small distinction can greatly impact how effectively you manage and secure your mobile fleet, influencing productivity, data protection, and overall compliance.

Have you seen the new Groups feature in CFEngine Enterprise Mission Portal? It was first released in 3.23.0 and it’s part of the 3.24 LTS series released earlier this year, let’s check it out. Groups in Mission Portal can be based on any host reported data. They can be dynamic (hosts can come and go from a group) or they can be static and tied to specific hosts by hostname, mac address, IP or CFEngine’s public key.

SOC-2 is a critical framework that ensures the security, availability, integrity, confidentiality, and privacy of systems and data. It is particularly important for organizations handling sensitive customer information. If you are using any cloud vendor, especially AWS, and aiming for SOC-2 certification then this article is for you. We will provide insights into how AWS supports SOC-2 compliance, and also go through a comprehensive roadmap and practical strategies for meeting these essential standards.

In early 2025, Puppet will begin to ship any new binaries and packages developed by our team to a private, hardened, and controlled location. Our intention with this change is not to limit community access to Puppet source code, but to address the growing risk of vulnerabilities across all software applications today while continuing to provide the security, support, and stability our customers deserve.