
上QQ阅读APP看书,第一时间看更新
Implementation
Deep Security follows a client-server architecture, where every server that needs to be protected must have an agent installed that will communicate with the Deep Security Manager that is running either on-premise or maybe a SaaS-based solution.
From their official website, you can get a 30-day trial for a Deep Security SaaS solution, and you can go ahead and experiment with all the modules that are a part of the offering.
After you do a service discovery via AWS or install the agent on your servers, you will have a dashboard, where all the servers will be listed:

Each of the servers will have certain modules enabled. In my case, I have all the modules enabled except the Web Reputation one, as shown in the following diagram:
