Network Topology and Zones
Build a dynamic model of your network topology and define network zones.
The next step is to render a clear visual model of the network topology — what the devices are and where they are (i.e., specific IP addresses), the options for routing traffic throughout the network, how various points are connected, and so on. This model must be dynamic because your network is in a state of constant change. For example, your model might show that the enterprise application that serves electronic payment processing is on the same network segment as another business application. This is a direct conflict with PCI DSS requirements, which mandate that applications for processing credit card payments be completely isolated from all other applications on the network.
6 Steps for Ensuring Continuous Compliance in a Complex, Hybrid IT Environment
6 Steps for Ensuring Continuous Compliance in a Complex, Hybrid IT Environment
CISOs and their network security teams are under increasing pressure to adhere to an expanding "alphabet soup" of regulatory requirements that have a direct impact on the enterprise network. On top of that, every business has its own internal policies and best practice workflows to follow. One way to reduce the compliance enforcement and audit-readiness burden is to work toward the goal of continuous compliance — attaining a state where all compliance requirements are met, and then continuously maintaining that state.
Even with the many challenges of managing today's complex IT environment, it's possible to achieve continuous compliance through proper organization, thorough processes and technology automation. In this slideshow, Ellen Fischl Bodner, Tufin, has identified six steps that are critical to ensuring continuous compliance.
