You may be hearing a lot about SASE these days. That acronym stands for Secure Access Service Edge. Some IT folks pronounce it “sassy,” and it’s an architecture, not a product. In short, SASE enables you to combine networking and security functions into a single, seamless cloud-based architecture. This way you can provide secure access to all your organization’s data and apps from anywhere your users may be working.

IE has a new partner! F5 specializes in application delivery networking, application availability & performance, application security, multi-cloud management, network security, access & authorization, and online fraud prevention.

A zero-day critical security vulnerability affecting the Java logging library Apache Log4j service was first discovered on December 9th. This vulnerability can allow remote attackers to perform unauthenticated remote code execution and access to Apache web server, which are widely deployed and used in many products. Security researchers have observed hundreds of thousands of attempts to exploit this vulnerability since it was discovered. As such, organizations should take all measures necessary to mitigate this threat.

If you’re concerned about Zero Trust Architecture adoption, you’re not alone. It’s slowly becoming a necessity as cyber threats advance, and more companies do their business online. Zero Trust isn't a new concept. The term “Zero Trust” was initially published as part of a Forrester Research paper, “No More Chewy Centers: Introducing the Zero Trust Model of Information Security” in 2010. [1]

Disclaimer: To protect the privacy of a former client, I have changed key details of this story, however the main sentiment and methods remain the same. A few years ago, I orchestrated a jewel heist. Yes, you read that correctly. While claiming a mysterious former life of crime is always intriguing, the truth is it was all in the name of compliance and I had explicit (albeit less interesting) permission from the jeweler's CEO. Don’t get me wrong, I was no Box Man in this scenario. I didn’t need to be, especially since I’d been privy to the common security inconsistencies of the jeweler in question. My job was to create, deploy, and enforce security procedures. When I’d noticed that the employees had not been following these procedures as strictly as I’d recommended...I had to try a different tactic. I made my point the day I smuggled $20,000 in inventory from the main vault. The loss was enough to constitute a termination, and somehow this made them keener to heed my security warnings. They’d made a major procedural mistake by leaving the keys and safe combo in the same location. They’d served me the keys to the kingdom on a silver platter. It was the easiest $20,000 I’d ever made and my oh my did they learn their lesson! For the record, I returned the assets, but taking them had been too easy and it troubled me. In my experience as a compliance expert, I’ve seen lax attitudes and confusion surrounding information security programs. More specifically: the policies, standards, procedures, and guidelines that make up the program. While these components are often (wrongly) used interchangeably, there are very distinct differences between them, and each one should be taken seriously to maintain security protocols and protect your organization. Clearly defining the roles of each of these components and enforcing them within your workplace are essential for upholding a strong security posture. Before we dive into differentiating these four components, we need to first understand what an information security program is and why it is critical for your overall business operations.

Another week, another shortage it seems. COVID-19 conditioned us to expect this, but the most recent shortages (such as gasoline, beef, chicken, and pork) are due to cyber-attacks involving ransomware. The UK’s National Crime Agency (NCA) details that the overall threat from cybercrime has significantly increased in the past year [1].