ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

On a standalone agent, the history_ids.csv file does not get created after applying a detection policy

book

Article ID: 161743

calendar_today

Updated On:

Products

Embedded Security Critical System Protection

Issue/Introduction

 On a standalone agent, the history_ids.csv file does not get created after applying a detection policy. The history_ids.csv file contains records of policies that are accepted (successfully applied) or rejected. 

Resolution

Workaround: 

On Windows, use the Event Viewer to verify policy application. If a prevention policy is applied to the agent, you require permission in the policy to open the event viewer. 

See the Giving privileges to run the agent event viewer section in the online help. 
 
On Linux, see the SISIDSEvents.csv file to verify policy application. If a prevention policy is applied to the agent, you require to disable prevention in order to view the contents of the SISIDSEvents.csv file. 
 
Affected agent operating systems: All Windows and Linux operating systems
 

This issue has been resolved in Symantec™ Embedded Security: Critical System Protection release 1.0.1.