Utilizing security summary reports, we can start to build a picture of how secure our servers actually are. And based on those findings harden the systems to comply with any security codes we need to adhere to. The process is policy based and allows us to create our own, specific to internal requirements, or choose one pre-built by Idera, covering best practice advice or common security code specific protection.

Assessments were made by mapping security checks to corresponding risk level. So for any security requirements that we need to know about we can check for its compliance. We can see here an external cross reference. This field allows you to relate to security vulnerability included in your report to a number or name contained in your external security standard.

The selections made here will be used to investigate SQL servers and build a report of its current security risks. We can identify the server specifically that we want to analyze as well as adding to the report it will generate. And when we satisfied, click finish. This will create a policy which we can start gathering data and creating security assessments.

For more information on SQL Secure join us in the community at community.idera.com