There is a simple reason that an organization has recently experienced so many new vulnerabilities and breaches. Over the past year, organizations have transformed their endpoint environments, but continue to manage and protect their new environments with legacy tools designed for legacy environments.
What has changed in the latest endpoint environment
Historically, the endpoint environment was relatively small, static, and predictable. They were provisioned by IT and filled with endpoints that existed on-premises.
But over the past year, organizations have done the following:
- We have moved from the majority of on-premises environments to a mostly decentralized workforce. According to Pew Research Center findings, 71% of employees continue to work from home most or most of the time, compared to just 20% before the pandemic.
- Disbanded around them. The organization has spent more than a decade building defense in depth around on-premises employees. Still, the boundaries were designed only to manage and protect the endpoints within that wall, and became almost ineffective as soon as the user and that endpoint left the office.
- It flooded the environment with new endpoints, data, and connections. After COVID-19, according to a recent Statistica study, organizations increased the amount of frequently used devices by 11%, Confidential data 62% stored on the device and 176% adopted many collaboration apps.
Despite these major changes to the environment, many organizations continue to manage and Protect the endpoint Using legacy tools designed for older environments has disappointing results.
Why legacy tools cannot be applied to modern environments
To be clear, there are no fundamental issues with legacy endpoint tools. Yesterday’s endpoint tool worked well in yesterday’s endpoint environment.
However, when these tools are applied to today’s environments, they usually fail to perform basic endpoint management and security tasks. Specifically, these tools fail at some important point.
It is not easy to manage and protect a large, evolving environment filled with distributed endpoints.
Most legacy tools are built on a hub-and-spoke architecture and require dozens or hundreds of staging servers to perform simple endpoint management and security tasks. This structure prevents it from expanding rapidly along rapidly changing networks and consumes large amounts of bandwidth to scan large distributed networks and apply security controls. Organizations typically cannot afford this bandwidth, creating visibility gaps and lowering the level of compliance with simple controls.
You can’t provide the endpoint data your organization needs when you need it. Most legacy tools utilize centralized data acquisition and measurement. Every time you analyze endpoint data, you first need to get all the data from the network and store it in a central repository. However, today’s vast endpoint environment produces more data than legacy tools can quickly centralize. With traditional tools, organizations can no longer collect, store, and analyze endpoint data in an available way, requiring endpoint management and security decisions based on a limited, older dataset.
These tools make endpoint management and security unnecessarily complex and costly. Most legacy tools are designed to solve a single specific problem. This design typically requires an organization to adopt a new point tool each time it introduces a new asset type or vulnerability into the environment. These point tools do not work together and add complexity. The Ponemon Cyber Resilience Study recently found that 63% of security teams spend more time managing tools than fighting threats, and 53% actually worsen their security regime with an excessive amount of tools. I found that I think I am.
These are not minor points of failure. They suggest a fundamental discrepancy between legacy tools and modern environments.
Problems caused by legacy tools
To see how this fundamental discrepancy occurs in the real world, Surveyed hundreds of tech leaders About endpoint management and security tools and how
I will do it. We learned it:
- Technology leaders have dozens of endpoint tools. Most technology leaders (70%) use over 11 to 50 tools to manage and protect their endpoints. Almost half (46%) use 20 or more tools, and 20% use 30 or more tools. 4% of respondents do not know how many tools they are using.
- These tools are not effective. Many technology leaders do not collect the accurate real-time security data needed to assess and mitigate risk. Respondents said that the three most difficult risk-related tasks were gaining real-time visibility of data (88%), combining data from legacy on-premises and cloud infrastructure (79%), and accurate data. He said it was derived (77%).
- It’s time for a new, up-to-date endpoint tool. More than half (53%) of respondents are likely to rethink point tools in 2021 and integrate endpoint management and security tools to some extent or very likely. In addition, 59% of respondents believe that legacy on-premises infrastructure poses significant management challenges. Decentralized endpoints, 62% believe IT needs to modernize these tools and move their endpoint capabilities to the cloud.
- Traditional tools cannot manage or protect today’s new environment. They create issues that have contributed (if not completely) contributed to the increased breaches and vulnerabilities seen over the past year.
Modernization does not have to be complicated. Technology leaders simply replace legacy endpoint tools with the latest endpoint tools designed to perform management and security in today’s new environment.
Learn how to get Full visibility of all endpoints Perform large-scale actions within minutes.
IT Modernization: Why Old Solutions Can’t Secure Today’s Environments Source link IT Modernization: Why Old Solutions Can’t Secure Today’s Environments
The post IT Modernization: Why Old Solutions Can’t Secure Today’s Environments appeared first on California News Times.
