# RiskRecon
source: https://developer.mastercard.com/riskrecon-api/documentation/index.md

## Overview {#overview}

Ever-increasing cybersecurity threats expose your enterprise and third-party ecosystem to risks that could result in ransomware and breach events disrupting business continuity. The RiskRecon cybersecurity ratings and assessment platform uses cutting-edge artificial intelligence and data analytics to detect and prioritize vulnerabilities and rate the cyber health of your enterprise and third-party vendors across [9 security domains](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md#security-domain) and [37 security criteria](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md#security-criteria).

You can use RiskRecon APIs for your enterprise and third-party risk management and corresponding analytics. Using these APIs, you can retrieve data from the RiskRecon database regarding ratings, findings, action plans, TOEs, portfolio, alerts, breach events, and more.

## How It Works {#how-it-works}

The following diagram illustrates how RiskRecon builds TOEs for the customer's own enterprise and its third parties, monitors the entire portfolio to detect issues, prioritize them based on severity and asset values, assign ratings, and track remediation.

|        Actors         |                                                                                              Description                                                                                              |
|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Portfolio             | The portfolio is a collection of TOEs that are being analyzed for a customer.                                                                                                                         |
| Cybersecurity Analyst | The cybersecurity analyst is internal to RiskRecon and is responsible to build and periodically review the attribution of systems to the RiskRecon customer's own enterprise and their third parties. |
| API User              | Users of organizations having business relationships with RiskRecon use the RiskRecon APIs. For example, RiskRecon Alliance partners and RiskRecon customers.                                         |
| Scanner               | The RiskRecon scanner passively scans the systems across the customer's portfolio to gather raw cybersecurity data.                                                                                   |
| ETL                   | The RiskRecon Extract, Transform, and Load (ETL) engine.                                                                                                                                              |
| Database              | The ETL periodically updates the RiskRecon database with findings, ratings and processes related analytics which would be of use to the API user.                                                     |

![](https://static.developer.mastercard.com/content/riskrecon-api/uploads/howitworks.png)

### Workflow {#workflow}

* The API User, that is, the RiskRecon customer submits a bulk request to create TOEs.
* The RiskRecon cyber security analyst reviews the request, builds, and maintains the portfolio.
* The API User periodically checks the portfolio to see if the TOEs are added by performing search using the `TOE` endpoint, the internal name of the TOE, or its domain.   
  They also update the portfolio and the database by adding internal names or by adding TOEs through a quick add (`POST TOE`) or a bulk add (`POST Bulk Add`) request.
* The RiskRecon scanner periodically scans the portfolio and the systems of the customer and their third parties for issues.
* The ETL collates the raw data from the scanner into cybersecurity ratings across 9 security domains, 37 security criteria, and prioritized findings, each with their own asset values and severity.
* The ETL also updates the RiskRecon database with the findings, ratings, and other relevant information that the RiskRecon APIs and portal query against.

## Next Steps {#next-steps}

* [Glossary](https://developer.mastercard.com/riskrecon-api/documentation/glossary/index.md): To help you to get acquainted with the terminology used.
* [Getting Started](https://developer.mastercard.com/riskrecon-api/documentation/getting-started/index.md): To help you to know how to avail the RiskRecon services and to get a brief idea of the APIs used.
* [API Basics](https://developer.mastercard.com/riskrecon-api/documentation/api-basics/index.md): To help you to know how RiskRecon APIs implement authentication, authorization, encryption, and key management.
* [Tutorial and Guides](https://developer.mastercard.com/riskrecon-api/documentation/tutorials-and-guides/index.md): To help you to implement your solutions using the RiskRecon APIs.
* [Use Cases](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/index.md): To help you to know in detail how each RiskRecon endpoint works.
* [API Reference](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/index.md): To help you to download the yaml files and get details on each endpoint.
* [Code and Formats](https://developer.mastercard.com/riskrecon-api/documentation/code-and-formats/index.md): To help you to know RiskRecon API errors, and date and time formats.
* [Reference App](https://developer.mastercard.com/riskrecon-api/documentation/reference-app/index.md):
* [Testing](https://developer.mastercard.com/riskrecon-api/documentation/testing/index.md): To help you to understand each endpoint request and response with examples on successful and failed scenarios.
* [Support](https://developer.mastercard.com/riskrecon-api/documentation/support/index.md): To help you to seek answers on FAQs and how to avail technical support.