With the rising trend of digitization, major companies like Airbnb, Microsoft and Twitter are staying out of the office, moving processes online and allowing employees the option to work from home. Organizations are adopting remote and hybrid working models. As a result, many people are spending more than double the amount of time online as they did pre-pandemic.

I have always worked in tech, so have always needed to understand the technical nature of the products we are building. This process has always been over-complicated for me so I now always try to write a guide for non-technical people like me. It turns out that once you understand it you can explain it to other non-technical people much easier! So here we go as I try to explain SAML (Security Assertion Markup Language) SSO (single sign-on) and why BoxyHQ makes it so easy to implement.

This article follows my first article in which I explain the basics of SAML from the users' side. If you haven't read that one already I would recommend reading that one first here. In this article, we are going to take a look at what SAML authentication and setup look like from the solution providers' perspective. If you are a B2B solutions provider and you plan to have enterprise customers they will likely ask that your product supports SAML SSO.

Cloud computing is an effective solution for large and small companies across every industry. There has been rapid adoption due in large part to its accessibility, flexibility, and reliability. The cloud environment brings a significant amount of benefits, but at the same time, it can expose businesses to various alarming cybersecurity risks. A study conducted by Thales and 451 Research revealed that 40% of respondents have experienced a data breach within their cloud environments.

In this new world of hybrid work where users, data, and applications are everywhere, there has been an increased reliance on web-based applications and for good reason. Web apps allow greater accessibility, flexibility, and scalability of resources for users requiring access from anywhere. While web applications are great, IT teams oftentimes encounter onboarding issues, specifically around discovering unidentified domains, and easily defining new policies for those discovered resources.

“Why is Exchange so slow? I’ve checked everything in the O365 administration portal. The MTAs, the DB and the service are green. It must be networking! Can you check the network? I am sending the ticket to you!” The company I worked at previously was an early customer of the Exchange O365. And the company ran on email. Every message, file, PowerPoint and design document was sent via email. If email was not working, the company ground to a halt.

Multi-factor authentication (MFA) is an authentication method that requires at least two forms of verification of the user’s identity to gain access to an account, application, or data set. Instead of needing just a username and password to log in, MFA adds additional layers of security by requiring users to verify their identity. Each additional verification method can prevent unauthorized access from cybercriminals or hackers from executing a successful cyber attack.

You might think that the majority of cybersecurity breaches result from carefully planned and executed attacks. You may imagine hackers expertly crafting phishing emails to con employees into giving away access to critical systems, for example, or planting state-of-the-art malware on victims' servers. The reality – as Zenity co-founder and CTO Michael Bargury explains in his most recent Dark Reading column – is less interesting, and perhaps more worrying.