Skip to content
Was this article helpful?

si_safety_signature

Configuration for AF Safety Data Report table resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
sig_rule_id <Double> Read-write Signature Rule Id.
sig_none <Double> Read-write Signature None Flags..
configuration <String> Read-write Profile Security configuration.

Maximum length = 255
sig_log <Double> Read-write Signature Log Flag..
name <String> Read-write Profile Name.

Maximum length = 255
profile_not_block_count <Double> Read-write Count of Blocked Profile..
sig_log_count <Double> Read-write Count of Signature Logs.
sig_stat <Double> Read-write Signature Stats..
sig_learn <Double> Read-write Signature Learn Flag..
sig_block_count <Double> Read-write Count of Blocked Signatures.
sig_safety_index <Double> Read-write Signature Safety Index..
si_app_unit_name <String> Read-write AppName.

Maximum length = 255
__count <Double> Read-write Number of records.
id <String> Read-write Id is safety profile.

Maximum length = 255
sig_rule_category <String> Read-write Profile sig_rule_category.

Maximum length = 2550
sig_sig_name <String> Read-write Profile signature name.

Maximum length = 2550
sig_block <Double> Read-write Signature Block Flags..
profile_sig_disable_count <Double> Read-write Count of Disabled Profile Signatures..
sig_stat_count <Double> Read-write Count of Signature Stats..
sig_rule_logstring <String> Read-write Profile sig_rule_logstring.

Maximum length = 2550
profile_safety_index <Double> Read-write Profile Safety Index..

Operations

(click to see Properties )

  • GET (ALL)

Some options that you can use for each operations:

  • Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.

  • Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER: <username>

    X-NITRO-PASS: <password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN= <tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in green

The following parameters can be used in the nitro request : onerror <String_value>

Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.

Default value: EXIT

Possible values = EXIT, CONTINUE

get (all)

URL: https://<MGMT-IP>/nitro/v2/config/si_safety_signature

Query-parameters:

cr_enabled Use this query-parameter to indicate cr is enabled or not.

Possible Values: 0, 1

report_start_time Use this query-parameter to specify the start time from which the summary for report is considered.

Possible Values: time in milli seconds

report_end_time Use this query-parameter to specify the end time until where summary for report is considered.

Possible Values: time in milli seconds

asc Use this query-parameter to specify whether the results should be in ascending order or not.

Possible Values: yes, no

sla_enabled Use this query-parameter to indicate sla is enabled or not.

Possible Values: 0, 1

order_by Use this query-parameter to get the result that is ordered by the given property.

Possible Values: total_attacks, sig_rule_id

type Use this query-parameter to specify the type.

Possible Values: total_attacks, sig_rule_id

HTTPS Method: GET

Response:

HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "si_safety_signature":[{
      "sig_rule_id":<Double_value>,
      "sig_none":<Double_value>,
      "configuration":<String_value>,
      "sig_log":<Double_value>,
      "name":<String_value>,
      "profile_not_block_count":<Double_value>,
      "sig_log_count":<Double_value>,
      "sig_stat":<Double_value>,
      "sig_learn":<Double_value>,
      "sig_block_count":<Double_value>,
      "si_device_ip_address":<String_value>,
      "sig_safety_index":<Double_value>,
      "si_app_unit_name":<String_value>,
      "__count":<Double_value>,
      "id":<String_value>,
      "sig_rule_category":<String_value>,
      "sig_sig_name":<String_value>,
      "sig_block":<Double_value>,
      "profile_sig_disable_count":<Double_value>,
      "sig_stat_count":<Double_value>,
      "sig_rule_logstring":<String_value>,
      "profile_safety_index":<Double_value>}]}
Was this article helpful?