Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

As a CISO or Security Manager, you understand your organization’s need to remain one step ahead of cybercriminals searching for gaps in your security posture. The market is flooded with solutions for dealing with vulnerabilities and the challenge continues to be understanding the ways to best prioritize and manage the vulnerabilities.

As malicious attackers and nation states have increasingly weaponized the cyber domain to impact private companies, the sustainability of organizations' ties to their cybersecurity is in question across all industries and sectors. There are many examples of companies going out of business as a result of a cyber attack, due to business leaders failing to wrap their arms around all the different ways that the ever evolving cyber threat landscape can impact their business.

The SSH protocol offers multiple authentication options: passwords, public keys and certificates. Certificate-based authentication is the most secure of them all, but historically, it has been the most complicated to set up. This tutorial guides you through simple steps to configure certificate-based authentication for an OpenSSH server. First, let's consider the differences between certificates and keys. As you can see, an SSH key is a binary proposition.

Digital transformation has accelerated and zero-trust architecture has helped businesses invest in more advanced technologies without the risk of advanced cyberattacks. According to WatchGuard’s Pulse survey of 100 IT and security executives, a zero-trust framework stimulates digital transformation for companies, as stated by 6 out of 10 respondents (59%).

The security landscape is continually changing and the race to stay ahead is often one of both victory and failure. As organizations globally continue to expand, security professionals are struggling to update operations quickly enough to ensure effective monitoring and response to incidents in their environment. The lack of security professionals makes this even more challenging. Patching systems, scanning for vulnerabilities, protecting against malware and viruses are essential and just plain smart.

While EDRM is the only solution available to solve the security problems of unstructured data, oftentimes the term EDRM itself is the most dreaded one for many organizations. This is because many EDRM projects have failed miserably. These projects have failed because of overzealous policies, loss of control over the policies, and no proper implementation guidelines. This oftentimes leads to access being denied to those who are authorized to have access.

Remember how, just a few years ago, many organizations were striving to be cyber secure? Over the last years, it seemed that crowing about one’s cybersecurity posture became the very thing that mocked every organization that was the victim of a newsworthy compromise. Many organizations began augmenting their previously acclaimed security posture towards one of cyber resilience.

The Payment Card Industry Data Security Standard (PCI DSS) is a benchmark with tenure in the industry, with the first version being introduced in 2004. The PCI DSS was unique when it was introduced because of its prescriptive nature and its focus on protecting cardholder data. Cybersecurity is a changing landscape, and prescriptive standards must be updated to address those changes. The most recent update to the PCI DSS was in 2018, and the world has certainly changed since then.

When a business concept is born, building out a tech stack based on cybersecurity is not always the first item of concern. The need to simplify cybersecurity often comes later in the growth phase of a business. Start ups are well-known for everyone on staff pitching in in different areas. Technology, software purchases are often based on last minute needs, lowest costs, etc. It is often assumed that security is covered by the manufacturers of the chosen technology.

When security analysts choose technology, they approach the process like a mechanic looking to purchase a car. They want to look under the hood and see how the product works. They need to evaluate the product as a technologist. On the other hand, the c-suite has different evaluation criteria. Senior leadership approaches the process like a consumer buying a car.