In the Security and compliance studio, you can audit the security configuration in several ways. You can also generate a security history log report for audit or other compliance requirements.
Name | Responsible | Description |
---|---|---|
Initialize Security and compliance IT audit |
Security administrator |
During implementation, to make security configuration event logging possible, you initialize the Security and compliance studio IT audit. You initialize just once. You can also use this job to clean up the security log.
As a result:
|
Analyze security configuration history |
Security auditor |
In the Security and compliance studio, you can audit the security configuration in several ways:
Events done on the security configuration are logged in the security history. So, you can analyze the changes to the security configuration.
These events are logged:
|
Create security log report |
Security auditor |
You can generate a security history log report for audit or other compliance requirements. These compliance requirements can be internal or external. You can generate the report with:
|
Create security audit report |
Security auditor |
You can use the security audit report to analyze permissions and permission changes that are made to recorded elements during a specific period.
You can create the report based on:
You can only create this report if Security and compliance IT audit is initialized.
|
View Security and compliance studio data on person search report |
Security auditor |
For Security and compliance studio, an extension is added to the Person search report.
On the Person search report, in the Security and compliance studio results section, you can find this security information:
For more information, refer to Person search report. |