NetApp filers are added to a Data Governance Edition deployment as managed hosts with remote agents. When selecting an agent for scanning a NetApp filer, take the following into consideration:
FPolicy is required for Data Governance Edition to capture real-time security updates and to collect resource activity. In order to use FPolicy on NetApp 7-Mode managed hosts, CIFS file system protocol must be enabled.
When adding a NetApp 7-Mode managed host, you can use one of the following for FPolicy deployment:
- automatic FPolicy deployment
- use a pre-created FPolicy
However, for NetApp Cluster Mode managed hosts, FPolicy deployment is always automatic.
Using automatic FPolicy deployment for NetApp 7-Mode
When you add a NetApp managed host, an FPolicy is created if either of the following managed host settings are enabled:
- Collect activity for real-time security updates on the Security Scanning page
- Collect and aggregate events on the Resource Activity page
When you deploy an agent, an empty FPolicy (with no monitored operations) is created by the Data Governance server (performed as the service account for the domain). When the agent starts, it registers with the FPolicy as an FPolicy Server. At the point of registration, the agent will register the operations it will monitor.
Note: If another agent is added to the managed host to index a separate root on the NetApp device, a new FPolicy will be created (named after the new agent ID).
- is created using the credentials of the domain service account.
- is named after the agent ID (that is, DGE_ <DeploymentName>_<FQDN of managed host>).
- is configured to use the version 2 interface.
- includes cifs_set_attr information, which allows Data Governance Edition to receive notification of security changes.
- sets the cifs_setattr option to on (defaults to off in FPolicy).
Note: To view all the existing FPolicies on a NetApp device, establish a Telnet or SSH connection to the filer device, log in and type the following at the OnTap command line: “fpolicy”.
Note: When you remove an agent, the FPolicy is deleted.
Using a pre-created FPolicy on a NetApp 7-Mode filer
Data Governance Edition can be configured to connect to a pre-created FPolicy. The following steps are required to configure Data Governance Edition to use a manually created FPolicy instead of automatic deployment:
- Enable CIFS FPolicy on NetApp filer
- Create FPolicy on the filer
- Configure the Data Governance server and agent
To enable CIFS FPolicy on a NetApp filer
- Run options FPolicy.enable on
To create FPolicy on the filer
- fpolicy create <PolicyName> Screen
- fpolicy enable <PolicyName>
To configure the Data Governance server and agent
Configure the Data Governance server to prevent the creation of FPolicy on the required NetApp filer:
- Create the following registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Broadway\Server\ManualFPolicyCreation”.
- Add a string value with the fully qualified domain name of the NetApp filer.
In the Manager, deploy a NetApp managed host.
Note: Ensure that the registry key has been created on the server before deploying the agent.
- Configure the NetApp agent to use the manually pre-created FPolicy.
- Stop the agent service.
Locate the following configuration setting in the %Program Files%\One Identity\One Identity Manager Data Governance Edition\Agent Services\DataGovernance.Agent.exe.config file.
- Add a string value with the FPolicy name you want the specified agent to register with.
- Save the configuration file.
- Restart the agent.
FPolicy deployment for NetApp Cluster Mode
FPolicy deployment for NetApp Cluster Mode is always automatic and is done by the agent at run time because of the use of dynamic ports. The FPolicy will be deleted when the agent stops. You cannot specify a pre-created FPolicy.
During the configuration of the managed host:
- Select the required shares (managed paths) to scan.
- (Optional) Select to Collect activity for real-time security updates.
- (Optional) Select to Collect and aggregate resource activity.
When you add an agent, the managed host properties impact whether FPolicy is deployed, and what properties are set within the FPolicy itself:
- If both Collect activity for real-time security updates and Collect and aggregate activity are disabled on the managed host, FPolicy will not be created when the agent is deployed.
- If Collect activity for real-time security updates or Collect and aggregate activity is enabled, FPolicy will be created; however, there will be no registered settings until the agent starts up and receives the updated settings from the Data Governance servers.
- The agent must start its security scan before it registers with FPolicy. This means that managed paths must be set and the agent must hit its configured scanning schedule. (To force this scan, select the Immediately scan on agent restart or when managed paths change option and restart the agent.)
The following events are tracked on files and folders, as well as the identities associated with those events, when real-time security updates and/or resource activity collection is enabled:
- File create
- File rename
- File delete
- File write
- File open
- Setattr (Security changes including DACL, and Owner changes)
- Directory rename
- Directory delete
- Directory create
Enabling FPolicy on NetApp filers may impact system performance. Data Governance Edition uses 'async' mode and does not inspect any file data to try and minimize the performance impact. However, every event does require a round trip network request between the NetApp filer and the Data Governance agent.
Are rescans of all directory structures required to detect change?
To have Data Governance Edition watch for security changes, real-time security updates must be enabled. That is, select the Collect activity for real-time security updates option at the bottom of the Security Scanning page on the Managed Hosts Settings dialog for the target managed host. This will cause the FPolicy to be deployed and the security index to be updated when changes to the structure and security of the file system on the target managed host occur.