{"id":45410,"date":"2022-02-23T11:00:00","date_gmt":"2022-02-23T11:00:00","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/zero-trust-requires-clear-architecture-plans-before-changing-core-systems\/"},"modified":"2022-02-23T11:00:00","modified_gmt":"2022-02-23T11:00:00","slug":"zero-trust-requires-clear-architecture-plans-before-changing-core-systems","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/zero-trust-requires-clear-architecture-plans-before-changing-core-systems\/","title":{"rendered":"Zero trust requires clear architecture plans before changing core systems"},"content":{"rendered":"
<\/div>\n

Zero trust touches everything: identity, applications, networks, data, and devices. The best approach is not to change everything all at once. Instead, start with the big picture.<\/p>\n

In our research, we\u2019ve found the most successful organizations dedicated the first phase of their zero-trust initiatives<\/a> to working out an architecture. They didn\u2019t rush into deploying solutions as though starting with a greenfield.<\/p>\n

Everyone else dove in fast, mixing the foundational work on zero trust<\/a> with one or more of the knock-on efforts: rearchitecting networks, security, and data management; buying tools; forming implementation teams and setting them to work. All those things need to happen, of course, but with zero trust, it pays to do a lot more thinking about how all the pieces will fit together before undertaking the changes needed, either at the architectural level or in the tool set.<\/p>\n