fortinet.fortimanager.fmgr_ips_sensor module – Configure IPS sensor.
Note
This module is part of the fortinet.fortimanager collection (version 2.1.5).
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_sensor
.
New in version 2.10: of fortinet.fortimanager
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 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:
|
|
the top level parameters set |
|
Enable/disable malicious URL blocking. Choices:
|
|
Comment. |
|
Entries. |
|
Action taken with traffic in which signatures are detected. Choices:
|
|
Applications to be protected. set application ? lists available applications. all includes all applications. other includes all unlisted applications. |
|
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 (0 - 4294967295). |
|
Protect client or server traffic. |
|
Enable/disable logging of signatures included in filter. Choices:
|
|
Enable/disable logging of attack context: URL buffer, header buffer, body buffer, packet buffer. Choices:
|
|
Enable/disable packet logging. Enable to save the packet that triggers the filter. You can download the packets in pca… Choices:
|
|
Operating systems to be protected. all includes all operating systems. other includes all unlisted operating systems. |
|
Protocols to be examined. set protocol ? lists available protocols. all includes all protocols. other includes all unlisted protocols. |
|
Quarantine method. Choices:
|
|
Duration of quarantine. (Format ###d##h##m, minimum 1m, maximum 364d23h59m, default = 5m). Requires quarantine set to … |
|
Enable/disable quarantine logging. Choices:
|
|
Count of the rate. |
|
Duration (sec) of the rate. |
|
Rate limit mode. Choices:
|
|
Track the packet protocol field. Choices:
|
|
Identifies the predefined or custom IPS signatures to add to the sensor. |
|
Relative severity of the signature, from info to critical. Log messages generated by the signature include the severity. |
|
Status of the signatures included in filter. default enables the filter and only use filters with default status of en… Choices:
|
|
Enable/disable extended logging. Choices:
|
|
no description |
|
Action of selected rules. Choices:
|
|
no description |
|
no description |
|
Enable/disable logging of selected rules. Choices:
|
|
Enable/disable packet logging of selected rules. Choices:
|
|
Filter name. |
|
no description |
|
no description |
|
Quarantine IP or interface. Choices:
|
|
Duration of quarantine in minute. |
|
Enable/disable logging of selected quarantine. Choices:
|
|
no description |
|
Selected rules status. Choices:
|
|
Sensor name. |
|
no description |
|
Action of override rule. Choices:
|
|
no description |
|
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: 300 |
Notes
Note
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
- hosts: fortimanager00
collections:
- fortinet.fortimanager
connection: httpapi
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: Configure IPS sensor.
fmgr_ips_sensor:
bypass_validation: False
adom: ansible
state: present
ips_sensor:
block-malicious-url: disable
comment: 'ansible-comment'
name: 'ansible-test-ipssensor'
- name: gathering fortimanager facts
hosts: fortimanager00
gather_facts: no
connection: httpapi
collections:
- fortinet.fortimanager
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: retrieve all the IPS sensors
fmgr_fact:
facts:
selector: 'ips_sensor'
params:
adom: 'ansible'
sensor: ''
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The full url requested Returned: always Sample: “/sys/login/user” |
|
The status of api request Returned: always Sample: 0 |
|
The descriptive message of the api response Returned: always Sample: “OK.” |
Authors
Link Zheng (@chillancezen)
Jie Xue (@JieX19)
Frank Shen (@fshen01)
Hongbin Lu (@fgtdev-hblu)