Azure-Sentinel/Playbooks/HaveIBeenPwned
sindhuacc 980b128a5e trimmed the URL to make it as domain format in "Get site breaches enrichment" playbook and added domain as an optional parameter in custom connector action 2021-08-02 19:50:22 +05:30
..
HaveIBeenPwnedCustomConnector trimmed the URL to make it as domain format in "Get site breaches enrichment" playbook and added domain as an optional parameter in custom connector action 2021-08-02 19:50:22 +05:30
Playbooks trimmed the URL to make it as domain format in "Get site breaches enrichment" playbook and added domain as an optional parameter in custom connector action 2021-08-02 19:50:22 +05:30
HaveIBeenPwned.jpg HaveIBeenPwned Logic Apps connector 2021-07-26 18:42:55 +05:30
azuredeploy.json trimmed the URL to make it as domain format in "Get site breaches enrichment" playbook and added domain as an optional parameter in custom connector action 2021-08-02 19:50:22 +05:30
azuredeploylinkedtemplate.json updated metadata as per Lior's changes 2021-08-02 12:05:27 +05:30
readme.md update the custom connector response for "get all the pastes for an account" action and updated the consolidated readme file with the actual links of playbooks 2021-08-02 11:32:04 +05:30

readme.md

HaveIBeenPwned Logic Apps Custom Connector and playbook templates

HaveIBeenPwnedCustomConnector

Table of Contents

  1. Overview
  2. Deploy Custom Connector + 4 Playbook templates
  3. Authentication
  4. Prerequisites
  5. Deployment
  6. Post Deployment Steps
  7. References
  8. Limitations

Overview

Have I Been Pwned is a website that allows Internet users to check whether their personal data has been compromised by data breaches.

Deploy Custom Connector + 4 Playbook templates

This package includes:

  • Custom connector for HaveIBeenPwned.
  • Four playbook templates leverage HaveIBeenPwned custom connector.

You can choose to deploy the whole package : connector + all four playbook templates, or each one seperately from it's specific folder.

Deploy to Azure Deploy to Azure Gov

HaveIBeenPwned connector documentation

Authentication

Authentication methods this connector supports- API Key authentication

Prerequisites for using and deploying Custom Connector + 4 playbooks

  1. HaveIBeenPwned service end point should be known. (e.g. https://{haveibeenpwned.com})
  2. Generate an API key. Refer this link on how to generate the API Key

Deployment instructions

  1. Deploy the Custom Connector and playbooks by clicking on "Deploy to Azure" button. This will take you to deploying an ARM Template wizard.
  2. Fill in the required parameters for deploying custom connector and playbooks
Parameters Description
For Custom Connector
Custom Connector name: Enter the Custom connector name (e.g. contoso HaveIBeenPwned connector)
Service Endpoint: Enter the HaveIBeenPwned service end point (e.g. https://{haveibeenpwned.com})
For Playbooks
HaveIBeenPwned Enrichment GetAccountBreaches: Enter the playbook name for account breaches (e.g. HaveIBeenPwned Playbook)
HaveIBeenPwned Enrichment GetSiteBreaches: Enter the playbook name for site breaches (e.g. HaveIBeenPwned Playbook)
HaveIBeenPwned Response On Teams: Enter the playbook name for response on teams (e.g. HaveIBeenPwned Playbook)
HaveIBeenPwned Send Email : Enter the playbook name for sending email (e.g. HaveIBeenPwned Playbook)

Post-Deployment instructions

After deploying response from Teams playbook, we need to select the Teams group and Teams channel from the dropdown in logic app designer.

a. Authorize connections

Once deployment is complete, you will need to authorize each connection.

  1. Click the Teams connection resource
  2. Click edit API connection
  3. Click Authorize
  4. Sign in
  5. Click Save
  6. Repeat steps for other connections such as Office 365 connection and HaveIBeenPwned API Connection (For authorizing the HaveIBeenPwned API connection, API Key needs to be provided)

b. Configurations in Sentinel

  1. In Azure sentinel analytical rules should be configured to trigger an incident with risky user account or site.
  2. Configure the automation rules to trigger the playbooks.

Reference to the playbook templates and the connector

Connector *HaveIBeenPwnedCustomConnector

Playbooks

Known Issues and Limitations

  • We need to authorize the connections after deploying the playbooks.