# Retrieve Issue-based Alerts
source: https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md

## Overview {#overview}

Issue-based alerts notify you about newly observed issues or findings within your enterprise or your third-party risk portfolio. Once you subscribe to receive issue-based alerts, you can use the `GET Alerting Issues` endpoint to fetch alerting issues from new scans of your portfolio as per your alert settings or policies, which apply to your entire customer account across all users.
Note: Data Loss Events are not included in the `Alerting API` and the `Data Loss Events` endpoint is not affected by the user's breach event email notification settings.

### Filter parameters {#filter-parameters}

RiskRecon recommends using filtering capabilities to limit the amount of data that comes back in the response by using [pagination parameters](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/index.md#pagination-metadata) and the following query parameters in the API request:

* **Start date** and **End date**: You can search for alerting issues for a particular date range within a period of one month.
* **Priorities** : You can use the `priorities` array parameter to search for alerting issues as per their priority. For example, you might want to search priority 1 and priority 2 alerting issues to understand what action to take immediately.  

### Subscribe to issue-based alerts {#subscribe-to-issue-based-alerts}

To subscribe to issue-based alerts, the RiskRecon system administrator must enable an alert policy for your organization. You have to work with your RiskRecon system administrator to set or modify the issue-based alert policies.

The following are the steps necessary to retrieve issue-based alerts:

1. [Set issue-based alert policy](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#set-issue-based-alert-policy)
2. [Retrieve issue-based alerts](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issue-based-alerts)

## Set issue-based alert policy {#set-issue-based-alert-policy}

### Sequence Diagram {#sequence-diagram}

The following diagram shows how to set issue-based alerts:
Diagram set-issue-based-alerts1

### Execution Steps {#execution-steps}

The following steps describe a sample integration flow to enable the issue-based alert policy after logging into the RiskRecon web portal:

1. The user requests the RiskRecon system administrator to configure the issue-based alert policy.
2. The RiskRecon administrator configures the issue-based alert policy.

## Retrieve issue-based alerts {#retrieve-issue-based-alerts}

### Sequence Diagram {#sequence-diagram-1}

The following diagram shows how to retrieve issue-based alerts:
Diagram receive-issue-alerts

### Execution Steps {#execution-steps-1}

The following steps describe a sample integration flow to retrieve issue-based alerts:

1. The user sends the `GET` request to RiskRecon to receive the issue-based alerts.
2. RiskRecon provides issue-based alerts to the user.

## Sample Request and Response {#sample-request-and-response}

For a sample response of this API, see [Get issue-based alert](https://developer.mastercard.com/riskrecon-api/documentation/testing/alerting-samples/rcv-iss-alrts-smpl/index.md).

## Use Case Examples {#use-case-examples}

The use cases in this section discuss how you can use the `GET Alerting Issues` endpoint to retrieve newly observed issues on some of the criteria listed here. All these use cases use the *priorities* attribute in the parameter. This attribute filters all findings based on an asset value and severity.

* [Retrieve issues observed on Cotenant IP Hosting](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issues-observed-on-cotenant-ip-hosting)
* [Retrieve issues observed on HTTP Security Headers](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issues-observed-on-http-security-headers)
* [Retrieve issues observed on Application Server Patching](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issues-observed-on-application-server-patching)
* [Retrieve issues observed on Certificate Expiration](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issues-observed-on-certificate-expiration)
* [Retrieve issues observed on Unsafe Network Services](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-mgmt-issue-rmdfn/alerting/issue-based-alerting/index.md#retrieve-issues-observed-on-unsafe-network-services)

### Retrieve issues observed on Cotenant IP Hosting {#retrieve-issues-observed-on-cotenant-ip-hosting}

The use case here discusses how the Alerting Issues API can be used to retrieve issues observed on shared IP addresses. For example, the alert may state if the system uses an IP address shared with other companies, impacting ability to control IP reputation and overall system security of the vendor or the customer. Such shared IP addresses may lead stealing of sensitive and confidential information by hackers.

### Retrieve issues observed on HTTP Security Headers {#retrieve-issues-observed-on-http-security-headers}

The use case here discusses how the Alerting Issues API can be usd to retrieve issues observed on missing security headers. For example, the alert here may state missing security headers which might allow hackers to inject inform or code to attack and steal data from the customer's or vendor's systems.

### Retrieve issues observed on Application Server Patching {#retrieve-issues-observed-on-application-server-patching}

The use case here discusses how the Alerting Issues API can be used to retrieve issues observed on application server patching. For example, the alert may state that the application server path software is not vulnerable but is no longer supported by the vendor.

### Retrieve issues observed on Certificate Expiration {#retrieve-issues-observed-on-certificate-expiration}

The use case here discusses how the Alerting Issues API can be used to retrieve issues observed on certification expiration. For example, the alert may state if the encryption certificate validity has expired resulting in a certificate error message which undermine the authenticity of the system.

### Retrieve issues observed on Unsafe Network Services {#retrieve-issues-observed-on-unsafe-network-services}

The use case here discusses how the Alerting Issues API can be used to retrieve issues observed on unsafe network services. For example, a vendor's system exposes an unsafe and inappropriate network service to the internet and immediate action needs to be taken to prevent compromise of the vendor's and the customer's systems.

## Endpoint {#endpoint}


API Reference: `GET /v1/alerting/issues`