Table of Contents
Advertisement
5 Add notes to the Notes tab of the Documentation frame as necessary to document progress or
necessary deviations from the recommended implementation steps.
6 When the implementation is complete, select the control and change the status drop-down to
Implemented.
An audit event is generated and sent to the Sentinel Control Center.
Because of potential legal and regulatory implications, the status for a control should only be
changed after all of the implementation steps have been successfully completed.
NOTE: A control must be installed before it can be implemented.
14.3.5 Testing Controls
After the content implementation, the content should be tested to verify that it is working as
expected. Testing might require steps such as the following:
Run a report.
Generate a failed login on a critical server and verify that a correlated event is created.
These steps should be added when the Solution Pack is created in Solution Designer.
To test a control:
1 Open a Solution Pack in Solution Manager.
2 Select a control.
3 Click the Testing tab in the Documentation frame.
4 Follow all of the instructions in the Testing tab.
5 Add notes to the Notes tab of the Documentation frame as necessary to document progress or
necessary deviations from the recommended testing steps.
6 When the testing is complete, select the control and change the status drop-down to Tested.
An audit event is generated and sent to the Sentinel Control Center.
Because of potential legal and regulatory implications, the status for a control should only be
changed after all of the testing steps have been successfully completed.
NOTE: A control must be installed and should be implemented before it can be tested.
14.3.6 Uninstalling Controls
Controls are often used to meet legal or regulatory requirements. After they are implemented and
tested, controls should be uninstalled only after careful consideration.
326 Sentinel 6.1 Rapid Deployment User Guide
Advertisement
Table of Contents
