Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About user risk score
- About bulk assignment of custodians
- Configuring Metadata Framework
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Adding a directory service domain to Data Insight
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp 7-mode file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp 7-mode file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Configuring monitoring of Box accounts
- Configuring monitoring of cloud sources in Data Insight
- Configuring OneDrive account monitoring
- Managing cloud sources
- Configuring monitoring of Box accounts
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Data Insight best practices
- Appendix B. Migrating Data Insight components
- Appendix C. Backing up and restoring data
- Appendix D. Data Insight health checks
- About Data Insight health checks
- About Data Insight health checks
- Appendix E. Command File Reference
- Appendix F. Data Insight jobs
- Appendix G. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Configuring Audit Events in AWS
While configuring Event Monitoring of S3 account in Data Insight, you need details like Athena Output Bucket Name, Athena Database, and Athena Table.
To get all those required details,
- Log in to the Cloudtrail console at https://console.aws.amazon.com/cloudtrail/
- Click Create a trail
- On the Choose Trail attributes page,
Enter Trail Name
Select New S3 bucket
Copy the location specified in the Logs will be stored field. You will need this location while creating the Athena Table.
Note:
These files will not be deleted by Data Insight. If required, delete files manually or automatically by creating a policy.
Enable Log file SSE-KMS encryption and provide an existing or new AWS KMS key, if you want to encrypt the log files
Disable Log file SSE-KMS encryption option if you do not want to encrypt the log files.
Enable Log file validation option.
Do not select anything in the CloudWatch Logs and Tags sections.
- Click Next.
- On the Choose Log Events page,
Select Data Events in the Events section.
Click Switch to advanced event selectors in the Data Events section.
Select S3 from the Data Event Type drop-down.
Select Custom from the Log selector template drop-down.
Enter a name in the Selector Name field.
For Advanced event selectors option, refer the table below:
Field
Operator
Value
eventName
does not start with
Head
eventName
does not start with
List
Points to remember:
If events of few buckets are required, add desired bucket details individually (add / at the end of every bucket). For example field:resources.ARN Operator:starts with Value:arn:aws:s3:::<bucket_name>/
If you want to avoid individual entries for few buckets, use common expression starts with and ends with if bucket naming convention allows the operation.
- Click Save changes to create a new Trail
After completing the procedure, a new log file (.json.gz) will be created every 5 minutes at the Trail log bucket.