# Issues#FindIssueById Find Security Issue by ID Endpoint: GET /sto/api/v2/issues/{id} Version: 1.0 Security: ## Query parameters: - `accountId` (string, required) Harness Account ID Example: "abcdef1234567890ghijkl" - `orgId` (string, required) Harness Organization ID Example: "example_org" - `projectId` (string, required) Harness Project ID Example: "example_project" - `targetId` (string) Associated Target ID Example: "abcdef1234567890ghijkl" ## Path parameters: - `id` (string, required) The ID of the Security Issue to retrieve Example: "abcdef1234567890ghijkl" ## Header parameters: - `X-Api-Key` (string) Harness personal or service access token Example: "Delectus et." ## Response 200 fields (application/json): - `baseImageName` (string) base image name of the issue Example: "baseImageName" - `baselineVariantId` (string) The Baseline Target Variant related to this Security Issue Example: "abcdef1234567890ghijkl" - `created` (integer, required) Unix timestamp at which the resource was created Example: 1651578240 - `currentStatus` (string) Current status of the Exemption Enum: "Pending", "Approved", "Rejected", "Expired" - `details` (object, required) Issue details common to all occurrences Example: {"package":"json-schema","version":"v0.2.3"} - `exemptionCoverage` (string) Indicates if the Security Issue was found to be Exempted, Partially Exempted. Example: "Partially Exempted" - `exemptionId` (string) ID of the associated Exemption Example: "abcdef1234567890ghijkl" - `exemptionStatusAtScan` (string) Exemption's status at the Security Scan created time Enum: "Pending", "Approved", "Rejected", "Expired" - `harnessAugmentation` (object) Harness Augmentation details Example: {"Est modi quis nam ipsam at.":"Provident dolores molestiae eos magnam."} - `id` (string, required) Resource identifier Example: "abcdef1234567890ghijkl" - `key` (string, required) Compression/deduplication key Example: "json-schema@0.2.3" - `numOccurrences` (integer) Indicates the number of Occurrences on the Issue Example: 10 - `occurrenceId` (integer) Example: 12345 - `occurrences` (array) Array of details unique to each occurrence Example: [{"line":"42"},{"line":"666"}] - `originStatus` (string) The status of the origin, either 'approved' or 'unapproved' Example: "approved" - `origins` (array) The origins of the issue Example: ["app","base"] - `productId` (string, required) The scan tool that identified this Security Issue Example: "product1234567890abcde" - `severity` (number, required) Numeric severity, from 0 (lowest) to 10 (highest) Example: 8.5 - `severityCode` (string, required) Severity code Enum: "Critical", "High", "Medium", "Low", "Info", "Unassigned" - `status` (string) Indicates if the Security Issue was found to be remediated, ignored, etc. Enum: "Remediated", "Compensating Controls", "Acceptable Use", "Acceptable Risk", "False Positive", "Fix Unavailable", "Exempted" - `subproduct` (string) The subproduct that identified this Security Issue Example: "product" - `targetId` (string) The Target that this Security Issue affects Example: "abcdef1234567890ghijkl" - `targetName` (string) The Name of the Target that this Security Issue affects Example: "abcdef1234567890ghijkl" - `targetType` (string) The type of the Target that this Security Issue affects Enum: "container", "repository", "instance", "configuration" - `targetVariantId` (string) The Target Variant that this Security Issue affects Example: "abcdef1234567890ghijkl" - `targetVariantName` (string) Name of the associated Target and Variant Example: "nodegoat:master" - `title` (string, required) Title of the Security Issue Example: "json-schema@0.2.3 is vulnerable to Prototype Pollution" - `type` (string) The type of vulnerability or quality issue for this Issue Enum: "SAST", "DAST", "SCA", "IAC", "SECRET", "MISCONFIG", "BUG_SMELLS", "CODE_SMELLS", "CODE_COVERAGE", "EXTERNAL_POLICY" ## Response 400 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404 ## Response 401 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404 ## Response 403 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404 ## Response 404 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404 ## Response 429 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404 ## Response 500 fields (application/json): - `message` (string, required) Example: "Not Found" - `status` (integer) Example: 404