You can set up FSA jobs to scan databases. Specifically, the FSA can scan columns in database tables that contain text or binary data. Binary data refers to documents (such as MS Word files).
What are database events?
When the FSA scans a database table, the scanned data is written to XML blob files. The FSA then passes these blob files to policy engines for processing.
Policy engines then apply Data At Rest triggers to the scanned data. If a trigger fires, a database event is generated and stored on the CMS. You can view these events in the iConsole; they are indicated by 
icons in the Search Results screen.
How does the FSA create database events?
By default, all scanned data in the table (each column for every row) is written to a single XML blob file and stored as a single event. However, for very large database tables, this is clearly undesirable. Instead, you can configure the FSA to slice the scanned data into smaller, more easily manageable events.
For example, you can specify a maximum number of rows per event, or a maximum size (in KB) per event. You can also configure special handling for binary data; for example, if a database table contains MS Word documents, you can specify that these documents are stored as attachments to database events.
How does the FSA connect to a database?
When you create a scanning job, the FSA generates a database connection string, based on the detail that you supply in the Job Definition wizard.
Important: If scanning Oracle databases, be aware that Oracle user, schema and table names are case-sensitive when you specify the connection string!
What data is captured?
When setting up a database scanning job, you can specify how binary data is handled.
Similarly, when you set up user policies, the Capture File Details? setting in each Data At Rest capture action determines what data is captured and stored on the CMS.
|
Copyright © 2014 CA.
All rights reserved.
|
|