Security Monitoring Overview
- Print
- PDF
Security Monitoring Overview
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Security Monitoring API is provided in a RESTful format. To call the provided API, a Sub Account and an Access Key are required.
API URL
POST
Classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1
VPC : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1
API
Service | API | Method | Request URI |
---|---|---|---|
Security Monitoring | getIDSList | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getIDSList - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getIDSList |
Security Monitoring | getIDSEventDetail | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getIDSEventDetail - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getIDSEventDetail |
Security Monitoring | getAVList | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getAVList - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getAVList |
Security Monitoring | getIPSList | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getIPSList - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getIPSList |
Security Monitoring | getWAFList | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getWAFList - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getWAFList |
Security Monitoring | getDDoSList | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getDDoSList - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getDDoSList |
Security Monitoring | getDDoSEventDetail | POST | - classic : https://securitymonitoring.apigw.ntruss.com/securitymonitoring/v1/getDDoSEventDetail - vpc : https://securitymonitoring.apigw.ntruss.com/vsecuritymonitoring/v1/getDDoSEventDetail |
Request headers
The following are the request headers for IAM authentication.
Header name | Description |
---|---|
x-ncp-apigw-timestamp | Time elapsed in milliseconds since January 1, 1970, 00:00:00 UTC If the time difference compared to the API Gateway server is more than 5 minutes, then the request is considered invalid |
x-ncp-iam-access-key | API Key issued from NAVER Cloud Platform or AccessKey issued from IAM |
x-ncp-apigw-signature-v2 | A signature that encrypts the request path and header with a SecretKey mapped to an AccessKey HMAC encryption algorithm uses HmacSHA256 See Call API that requires IAM authentication |
Errors
HTTP response code | returnCode | returnMessage |
---|---|---|
200 | 0 | SUCCESS |
200 | 9 | Internal Error Acquired. |
403 | -1 | Permission Denied. |
Common errors
HTTP response code | ErrorCode | ErrorMessage |
---|---|---|
400 | 100 | Bad Request Exception |
401 | 200 | Authentication Failed |
401 | 210 | Permission Denied |
404 | 300 | Not Found Exception |
429 | 400 | Quota Exceeded |
429 | 410 | Throttle Limited |
429 | 420 | Rate Limited |
413 | 430 | Request Entity Too Large |
503 | 500 | Endpoint Error |
504 | 510 | Endpoint Timeout |
500 | 900 | Unexpected Error |
Was this article helpful?