In today's world, data is the lifeblood of every organization. From intellectual property to employee and customer data to competitive intelligence and more — if your data is stolen, it's your reputation, money, and business on the line. But the way we store and interact with data has changed over the years. It's no longer located inside a perimeter, on networks and devices your organization has total control over.

The software bill of materials (SBOM) is quickly becoming an essential aspect of open source security and compliance. In this post, we'll delve into what SBOMs are, why they're necessary, and their role in open source security.

Today’s business world is more interconnected than ever. Communication gaps between teams, limited access to crucial data, and the inability to adapt swiftly to market shifts become pain points that slow down progress and hinder critical business decision-making. The Egnyte Mobile App is designed to address communication and collaboration challenges on-the-go.

The Internet of Things (IoT) has ushered in an era where devices are interconnected across the internet, enabling them to communicate and share data with ease. This innovation has dramatically transformed everyday life, introducing conveniences that were once the stuff of science fiction. Now, we can monitor our homes through cameras connected to our networks, control appliances from our smartphones, and receive real-time updates from our cars and health-monitoring smartwatches.

In the fast-paced world of application development, the use of open source components offers a quick path to building sophisticated applications. However, this approach introduces critical questions about software composition, licensing, and security. Before pushing any new application to production or even staging, the security and compliance teams alongside the application owner must address the following: This is where the importance of a Software Bill of Materials (SBOM) becomes clear.

In today’s interconnected digital landscape, robust IAM (Identity and Access Management) practices are critical pillars of an organization’s cybersecurity strategy. IAM serves as the fortress guarding sensitive data, applications, and systems from unauthorized access or breaches. Implementing top-tier IAM practices ensures not only data protection but also compliance adherence and streamlined user access.

In the swiftly evolving landscape of technology, cloud computing stands as a pivotal innovation, reshaping how we store, access, and manage data across the digital expanse. This paradigm shift towards cloud services offers unparalleled efficiency and flexibility, transforming the very foundation of our digital interactions. However, this transition also introduces complex security challenges that demand a nuanced and proactive approach to safeguard sensitive information against cyber threats.

Generative AI (à la OpenAI’s GPT and the likes) is a powerful tool for summarizing information, transformations of text, transformation of code, all while doing so using its highly specialized ability to “speak” in a natural human language. While working with GPT APIs on several engineering projects an interesting idea came up in brainstorming, how well would it work when asked to describe information provided in raw JSON into natural language?

It’s a Sunday morning and things are pretty quiet around the Fusilero household, which is especially noticeable now that the chaos of the holiday season has passed and the kids are back at school. So, I’m catching up on my reading and research – starting with Splunk Predictions 2024.

As more organizations collectively progress toward adopting a SASE architecture, it has become clear that the traditional SASE market definition (SSE + SD-WAN) is not enough. It forces some teams to work with multiple vendors to address their specific needs, introducing performance and security tradeoffs. More worrisome, it draws focus more to a checklist of services than a vendor’s underlying architecture.