This article outlines the process for utilizing the paging option to identify API records that exceed 1000.

1. By using the default GET All option, you can retrieve a maximum of 1000 entries. If you need to retrieve more than 1000 entries, you must use the pagination option.

2. Paging must be added at the end of the query.

?paging=(start eq 5, limit eq 10)

• To fetch 10 records starting from the 5th position

https://x.x.x.x/api/juniper/sd/ips-signature-management/ips-signatures?paging=(start eq 5, limit eq 10)

• To fetch 1000 records starting from the 3000th position

https://x.x.x.x/api/juniper/sd/ips-signature-management/ips-signatures?paging=(start eq 3000, limit eq 1000)

SAMPLE REST REQUEST
https://x.x.x.x/api/juniper/sd/ips-signature-management/ips-signatures?paging=(start eq 5, limit eq 10)

SAMPLE REST RESPONSE

{
    "ips-signatures": {
        "ips-signature": [
            {
                "recommended": false,
                "id": xxxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that has a client HW address (the MAC address for Ethernet) field that is not NULL terminated. RFC-2131 specifies that this field must be NULL terminated. ",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Info",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that has an unknown HW type. For Ethernet, the HW Type is 1. ",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Info",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that has an unknown opcode. The RFC specifies only the REQUEST and REPLY opcodes. This can be a malformed packet or indicate tunneling over the DHCP port.",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Info",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that has an invalid HW length. For Ethernet, the HW length should be 6 (the length of a MAC address).",
                "domain-id": 1,
                "cves": "yyyyy",
                "name": "xxxxxxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Major",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that has an invalid message type. RFC-2131 specifies message types 1 through 9.",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Major",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message with an invalid magic cookie. RFC-2131 specifies that all DHCP messages should have a magic cookie of 0x63825363 to distinguish between BOOTP and DHCP messages.",
                "domain-id": 1,
                "cves": "yyyyy",
                "name": "xxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Major",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP message that does not have the magic cookie. RFC-2131 specifies that all DHCP messages should have a magic cookie of 0x63825363 to distinguish between BOOTP and DHCP messages.",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Info",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly is a DHCP server reply that does not have the source port set to 67 in the UDP header.",
                "domain-id": 1,
                "cves": "",
                "name": "xxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Info",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "xxxx",
                "description": "This protocol anomaly is a DHCP message that does not have an End Of Options (tag 255). This can be a truncated UDP message or an attempt by a malicious client to exploit the server.",
                "domain-id": 1,
                "cves": "yyyyy",
                "name": "xxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "cts",
                "severity": "Major",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:25",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            },
            {
                "recommended": false,
                "id": xxxxx,
                "sig-type": "anomaly",
                "certs": "",
                "bugs": "",
                "description": "This protocol anomaly triggers when it detects a DHCP option that has an invalid length. RFC-1533 and RFC-1497 specify standard lengths for DHCP options.",
                "domain-id": 1,
                "cves": "yyyyy",
                "name": "xxxxx",
                "performance": "0",
                "service": "DHCP",
                "direction": "any",
                "severity": "Major",
                "recommended-action": "",
                "category": "DHCP",
                "definition-type": "PREDEFINED",
                "activation-date": "2003-04-22 21:55:26",
                "uri": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "href": "/api/juniper/sd/ips-signature-management/ips-signatures/xxxxx",
                "ageOfAttack": ""
            }
        ],
        "uri": "/api/juniper/sd/ips-signature-management/ips-signatures",
        "total": xxxxx
    }
}

3. If the issue persists, please contact JTAC for further support