fortinet.fortimanager.fmgr_dlp_profile module – Configure DLP profiles.
Note
This module is part of the fortinet.fortimanager collection (version 2.8.0).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install fortinet.fortimanager.
To use it in a playbook, specify: fortinet.fortimanager.fmgr_dlp_profile.
New in fortinet.fortimanager 2.1.0
Synopsis
This module is able to configure a FortiManager device.
Examples include all parameters and values which need to be adjusted to data sources before usage.
Parameters
Parameter |
Comments |
|---|---|
The token to access FortiManager without using username and password. |
|
The parameter (adom) in requested url. |
|
Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters. Choices:
|
|
The top level parameters set. |
|
Comment. |
|
Enable/disable DLP logging. Choices:
|
|
Enable/disable extended logging for data leak prevention. Choices:
|
|
Flow/proxy feature set. Choices:
|
|
Protocols to always content archive. Choices:
|
|
Enable/disable NAC quarantine logging. Choices:
|
|
Name of the DLP profile. |
|
Replacement message group used by this DLP profile. |
|
Rule. |
|
Action to take with content that this DLP profile matches. Choices:
|
|
Enable/disable DLP archiving. Choices:
|
|
Quarantine duration in days, hours, minutes |
|
Match files this size or larger |
|
Select the number of a DLP file pattern table to match. |
|
Select the type of content to match. Choices:
|
|
ID. |
|
MIP label dictionary. |
|
Percentage of fingerprints in the fingerprint databases designated with the selected sensitivity to match. |
|
Filter name. |
|
Check messages or files over one or more of these protocols. Choices:
|
|
(list) Select a DLP file pattern sensitivity to match. |
|
(list) Select DLP sensors. |
|
Select the severity or threat level that matches this filter. Choices:
|
|
Select whether to check the content of messages Choices:
|
|
Protocols to always log summary. Choices:
|
|
Enable/Disable logging for task. Choices:
|
|
Authenticate Ansible client with forticloud API access token. |
|
The overridden method for the underlying Json RPC request. Choices:
|
|
The rc codes list with which the conditions to fail will be overriden. |
|
The rc codes list with which the conditions to succeed will be overriden. |
|
The directive to create, update or delete an object. Choices:
|
|
The adom to lock for FortiManager running in workspace mode, the value can be global and others including root. |
|
The maximum time in seconds to wait for other user to release the workspace lock. Default: |
Notes
Note
Starting in version 2.4.0, all input arguments are named using the underscore naming convention (snake_case). Please change the arguments such as “var-name” to “var_name”. Old argument names are still available yet you will receive deprecation warnings. You can ignore this warning by setting deprecation_warnings=False in ansible.cfg.
Running in workspace locking mode is supported in this FortiManager module, the top level parameters workspace_locking_adom and workspace_locking_timeout help do the work.
To create or update an object, use state present directive.
To delete an object, use state absent directive.
Normally, running one module can fail when a non-zero rc is returned. you can also override the conditions to fail or succeed with parameters rc_failed and rc_succeeded
Examples
- name: Example playbook (generated based on argument schema)
hosts: fortimanagers
connection: httpapi
vars:
ansible_httpapi_use_ssl: true
ansible_httpapi_validate_certs: false
ansible_httpapi_port: 443
tasks:
- name: Configure DLP profiles.
fortinet.fortimanager.fmgr_dlp_profile:
# bypass_validation: false
workspace_locking_adom: <value in [global, custom adom including root]>
workspace_locking_timeout: 300
# rc_succeeded: [0, -2, -3, ...]
# rc_failed: [-2, -3, ...]
adom: <your own value>
state: present # <value in [present, absent]>
dlp_profile:
comment: <string>
dlp_log: <value in [disable, enable]>
extended_log: <value in [disable, enable]>
feature_set: <value in [flow, proxy]>
full_archive_proto:
- "smtp"
- "pop3"
- "imap"
- "http-post"
- "http-get"
- "ftp"
- "nntp"
- "mapi"
- "ssh"
- "cifs"
nac_quar_log: <value in [disable, enable]>
name: <string>
replacemsg_group: <string>
rule:
-
action: <value in [log-only, block, quarantine-ip, ...]>
archive: <value in [disable, enable]>
expiry: <string>
file_size: <integer>
file_type: <string>
filter_by: <value in [fingerprint, sensor, encrypted, ...]>
id: <integer>
label: <string>
match_percentage: <integer>
name: <string>
proto:
- "smtp"
- "pop3"
- "imap"
- "http-post"
- "http-get"
- "ftp"
- "nntp"
- "mapi"
- "ssh"
- "cifs"
sensitivity: <list or string>
sensor: <list or string>
severity: <value in [info, low, medium, ...]>
type: <value in [file, message]>
summary_proto:
- "smtp"
- "pop3"
- "imap"
- "http-post"
- "http-get"
- "ftp"
- "nntp"
- "mapi"
- "ssh"
- "cifs"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
The result of the request. Returned: always |
|
The full url requested. Returned: always Sample: |
|
The status of api request. Returned: always Sample: |
|
The api response. Returned: always |
|
The descriptive message of the api response. Returned: always Sample: |
|
The information of the target system. Returned: always |
|
The status the request. Returned: always Sample: |
|
Warning if the parameters used in the playbook are not supported by the current FortiManager version. Returned: complex |