V-241163

Discussion

Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the system. Changes to information system configurations can have unintended side effects, some of which may be relevant to security. Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the application. Examples of security responses include, but are not limited to the following: halting application processing; halting selected application functions; or issuing alerts/notifications to organizational personnel when there is an unauthorized modification of a configuration item.

Check Content

Review the Trend Deep Security server configuration to ensure organization-defined automated security responses are implemented if baseline configurations are changed in an unauthorized manner.

Deep Security, Policies, are policy templates that specify the security rules to be configured and enforced automatically for one or more computers. These compact, manageable rule sets make it simple to provide comprehensive security without the need to manage thousands of rules. Default Policies provide the necessary rules for a wide range of common computer configurations. 

1. Analyze the system using the Administration >> System Settings >> Alerts tab. Review the email address listed in the “Alert Event Forwarding (From The Manager).” 

If this email address is not present or does not belong to a distribution for system administrator and ISSOs, this is a finding.

2. Analyze the system using the Administration >> System Settings >> System Events tab to ensure the following events are enabled:

 350 Policy Created  Record Forward
 351 Policy Deleted  Record Forward
 352 Policy Updated  Record Forward
 353 Policies Exported Record Forward
 354 Policies Imported Record Forward

If the options for “Record” and “Forward” are not enabled on these events, this is a finding