--- title: "Get a IP reputation finding of a company." method: GET path: "/api/v2/companies/{id}/findings/ipreputation/{findingId}" tags: ["Findings"] --- # Get a IP reputation finding of a company. `GET /api/v2/companies/{id}/findings/ipreputation/{findingId}` The asset reputation score is based on the number of IPs or domains are blacklisted or that are used for sophisticated APT attacks. The reputation feeds are collected from VirusTotal, Cymon, Firehol, BlackList DNS servers, etc. This category has 7% effect on total scan score.

For storage optimization, the system permanently deletes all findings that haven't been detected by the Black Kite scanner for over a year. Findings with manually changed statuses or associated tickets are excluded. ## Path parameters - `id` integer, required - `findingId` integer, required ## Response `200` Success - IPReputationFinding - `FindingId` integer — The unique identifier of this finding. - `Domain` string — The domain which this finding is related. - `IPAddress` string — The related IP address which contains the finding. - `Severity` 'Info' | 'Low' | 'Medium' | 'High' | 'Critical' — The severity of a finding. - `Status` 'Active' | 'FalsePositive' | 'Suppressed' | 'Acknowledged' | 'Deleted' | 'Remediated' — The status of this finding. - Active, means the finding is still active with no review as of yet. - FalsePositive, means the finding is considered to be false alarm. - Suppressed, means the finding is suppressed, similar to FalsePositive. - Acknowledged, means the finding is accepted, for example will not be fixed. - Deleted, means the finding is deleted, similar to FalsePositive. - Remediated, means the finding is mitigated. - `ControlId` string — The unique identifier of the control that this finding relates to. - `Ticket` FindingTicketSummary — A summary information of a finding ticket. - `TicketId` number, nullable — The unique identifier of the ticket. - `Status` 'Unassigned' | 'Assigned' | 'In Progress' | 'Closed–Acknowledged' | 'Closed–Remediated' | 'Closed–False Positive' | 'On Hold' | 'Recheck' | 'Deleted' — The status of this ticket. A ticket is automatically in “Assigned” status when a user with admin rights assigns it to another user. Depending on the user type, tickets can have different statuses: In Progress, On Hold and Recheck. - Unassigned: No owner has been set; the ticket is pending assignment. - In progress: Means the user takes responsibility of the associated finding and in the remediation process. - On hold: Means the user is waiting for another action to be completed before s/he takes action with regards to the finding. - Recheck: Means the user has completed her/his progress about the finding and waits for the user who assigns the ticket (or follow-up user with admin rights) to close it. An admin user can set a ticket in seven different statuses, In Progress, On Hold, Recheck, Closed-Acknowledged, Closed-Remediated, Closed-False Positive, and Deleted. - Closed-Acknowledged: The definition is very similar to risk acceptance. This means no or limited action can be taken with regards to the finding. There is no way but to accept the risk of the finding. This could be due to an out-of-date system soon to be retired. - Closed–Remediated: The action right after the Recheck status. If a company user sets the ticket in Recheck status, it is then passed to the admin user for him/her to close the issue. Closed status means the issue is fixed. - Closed-False Positive: Indicates a reported issue was a false alarm upon investigation. No action needed, as it poses no genuine risk. - Deleted: As the name suggests, this deletes the ticket (not the finding). It does not necessarily mean the issue is fixed or risk is accepted. - `Owner` string, nullable — A ticket may have one or more owners. But this field contains the name or the email address of the first one. - `Category` string — The type of the black list that contains the IP address. OBSOLETE: Inspect ReputationListings field. - `FirstListingDate` string, date-time, nullable — The earliest date that the IP address blacklisted on the listing URL. - `ListingUrl` string — The black list URL that contains the IP address. OBSOLETE: Inspect ReputationListings field. - `Description` string — The short description of the black list that contains the IP address. OBSOLETE: Inspect ReputationListings field. - `ReportDate` string, date-time — The last date the IP address is seen in the blacklist along. NOTE: This field has the same value as the 'FindingDate' field. - `FindingDate` string, date-time — The last date the IP address is seen in the blacklist along. - `ReputationListings` ReputationFindingListings[] - `Category` string — The type of the black list that contains the IP address. - `Description` string — The short description of the black list that contains the IP address. - `Url` string — The black list URL that contains the IP address. - `Date` string, date — The black list listing date. - `ConfidenceLevel` 'Low' | 'Medium' | 'High' | 'VeryHigh', nullable — The confidence level of this finding. - `UpdateDate` string, date-time, nullable — The date that the finding was last updated. - `IsRsiFinding` boolean — Indicates whether this finding contributes to the company's Ransomware Susceptibility Index (RSI) score. ## Other responses - `401` — Unauthorized - `403` — Forbidden - `404` — Not Found - `default` — Failure --- [API](https://skmtc.net/blackkitetech/apis/black-kite-api.md) · [All operations](https://skmtc.net/blackkitetech/apis/black-kite-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/blackkitetech/black-kite-api/revisions/616dfa9b3b1f/schema)