fortinet.fortimanager.fmgr_ips_baseline_sensor module – Configure IPS sensor.
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_ips_baseline_sensor
.
New in fortinet.fortimanager 2.2.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:
|
|
Enable/Disable logging for task. Choices:
|
|
Authenticate Ansible client with forticloud API access token. |
|
The top level parameters set. |
|
Enable/disable malicious URL blocking. Choices:
|
|
Comment. |
|
Entries. |
|
Action taken with traffic in which signatures are detected. Choices:
|
|
(list) Applications to be protected. |
|
(list) List of CVE IDs of the signatures to add to the sensor |
|
Exempt ip. |
|
Destination IP address and netmask. |
|
Exempt IP ID. |
|
Source IP address and netmask. |
|
Rule ID in IPS database |
|
(list) Protect client or server traffic. |
|
Enable/disable logging of signatures included in filter. Choices:
|
|
Enable/disable logging of attack context Choices:
|
|
Enable/disable packet logging. Choices:
|
|
(list) Operating systems to be protected. |
|
(list) Protocols to be examined. |
|
Quarantine method. Choices:
|
|
Duration of quarantine. |
|
Enable/disable quarantine logging. Choices:
|
|
Count of the rate. |
|
Duration |
|
Rate limit mode. Choices:
|
|
Track the packet protocol field. Choices:
|
|
Identifies the predefined or custom IPS signatures to add to the sensor. |
|
(list) Relative severity of the signature, from info to critical. |
|
Status of the signatures included in filter. Choices:
|
|
Tags. |
|
Enable/disable extended logging. Choices:
|
|
Filter. |
|
Action of selected rules. Choices:
|
|
(list) Vulnerable application filter. |
|
Application |
|
(list) Vulnerability location filter. |
|
Location |
|
Enable/disable logging of selected rules. Choices:
|
|
Enable/disable packet logging of selected rules. Choices:
|
|
Filter name. |
|
(list) Vulnerable OS filter. |
|
Os |
|
(list) Vulnerable protocol filter. |
|
Protocol |
|
Quarantine IP or interface. Choices:
|
|
Duration of quarantine in minute. |
|
Enable/disable logging of selected quarantine. Choices:
|
|
(list) Vulnerability severity filter. |
|
Severity |
|
Selected rules status. Choices:
|
|
Log. Choices:
|
|
Sensor name. |
|
Override. |
|
Action of override rule. Choices:
|
|
Exempt ip. |
|
Destination IP address and netmask. |
|
Exempt IP ID. |
|
Source IP address and netmask. |
|
Enable/disable logging. Choices:
|
|
Enable/disable packet logging. Choices:
|
|
Quarantine IP or interface. Choices:
|
|
Duration of quarantine in minute. |
|
Enable/disable logging of selected quarantine. Choices:
|
|
Override rule ID. |
|
Enable/disable status of override rule. Choices:
|
|
Replacement message group. |
|
Block or monitor connections to Botnet servers, or disable Botnet scanning. Choices:
|
|
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 IPS sensor.
fortinet.fortimanager.fmgr_ips_baseline_sensor:
# 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]>
ips_baseline_sensor:
block_malicious_url: <value in [disable, enable]>
comment: <string>
entries:
-
action: <value in [pass, block, reset, ...]>
application: <list or string>
cve: <list or string>
exempt_ip:
-
dst_ip: <string>
id: <integer>
src_ip: <string>
id: <integer>
location: <list or string>
log: <value in [disable, enable]>
log_attack_context: <value in [disable, enable]>
log_packet: <value in [disable, enable]>
os: <list or string>
protocol: <list or string>
quarantine: <value in [none, attacker, both, ...]>
quarantine_expiry: <string>
quarantine_log: <value in [disable, enable]>
rate_count: <integer>
rate_duration: <integer>
rate_mode: <value in [periodical, continuous]>
rate_track: <value in [none, src-ip, dest-ip, ...]>
rule: <string>
severity: <list or string>
status: <value in [disable, enable, default]>
tags: <string>
extended_log: <value in [disable, enable]>
filter:
-
action: <value in [pass, block, default, ...]>
application: <list or string>
application_real: <string>
location: <list or string>
location_real: <string>
log: <value in [disable, enable, default]>
log_packet: <value in [disable, enable, default]>
name: <string>
os: <list or string>
os_real: <string>
protocol: <list or string>
protocol_real: <string>
quarantine: <value in [none, attacker, both, ...]>
quarantine_expiry: <integer>
quarantine_log: <value in [disable, enable]>
severity: <list or string>
severity_real: <string>
status: <value in [disable, enable, default]>
log: <value in [disable, enable]>
name: <string>
override:
-
action: <value in [pass, block, reset]>
exempt_ip:
-
dst_ip: <string>
id: <integer>
src_ip: <string>
log: <value in [disable, enable]>
log_packet: <value in [disable, enable]>
quarantine: <value in [none, attacker, both, ...]>
quarantine_expiry: <integer>
quarantine_log: <value in [disable, enable]>
rule_id: <integer>
status: <value in [disable, enable]>
replacemsg_group: <string>
scan_botnet_connections: <value in [disable, block, monitor]>
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 |