Feroot + PagerDuty Integration

Notify developers and security analysts when Feroot Inspector uncovers a malicious event and triggers alerts

Below is the step-by-step instructions on how to connect PagerDuty to Feroot and manage this integration

How it works

Feroot generates alerts if malicious JavaScript code or client-side vulnerabilities are detected. Alert events from Feroot trigger a new incident on the corresponding PagerDuty Service for Global Event Routing.

Requirements

The PagerDuty integration requires an admin role in order to authorize the account. If you are not an admin, please reach out to an admin or account owner within your organization to configure the integration for you.

Support

If you need any help getting the PagerDuty integration up and running, please do not hesitate to reach out to us via email at support@feroot.com

Integration walkthrough

In PagerDuty

There are two ways to integrate Feroot with PagerDuty. The first is via PagerDuty global event routing or via a PagerDuty service. If you are adding this integration to an existing PagerDuty service, please skip to the “Integrating with a PagerDuty Service” section of this guide.

Integrating with Global Event Routing

Integrating with Global Event Routing enables you to route events to specific services based on the payload of the event from Feroot.

  1. In the Configuration menu select Event Rules.
  2. On the Event Rules screen click on the arrow next to Incoming Event Source to display the Integration key information.
  3. Copy your Integration Key. This is the same integration key you will use for any other tool you want to integrate with using event rules. When you have finished setting up the integration in Feroot, you will return to this interface to specify how to route events from Feroot to services in PagerDuty.

Integrating with a PagerDuty Service

There are two ways to add an integration to a PagerDuty service:

Automatically – Which is completed using a simplified integration workflow. Please see the “In Feroot” section for more information.

Manually:

  1. There are two ways to add an integration to a service:
    • If you are adding your integration to an existing service: Click the name of the service you want to add the integration to. Then select the Integrations tab and click the New Integration button.
    • If you are creating a new service for your integration: Please read the documentation in the Configuring Services and Integrations section and follow the steps outlined in the Create a New Service section. You will need to select Feroot as the Integration Type in step 4. Continue with the “In Feroot” section (below) once you have finished these steps.
  2. Enter an Integration Name and select Feroot from the Integration Type menu.
  3. Click the Add Integration button to save your new integration. You will be redirected to the Integrations tab for your service.
  4. An Integration Key will be generated on this screen. Keep this key saved in a safe place, as it will be used when you configure the integration with Feroot in the next section.

In Feroot

  1. In your Feroot account, select the project that you would like to trigger incidents in PagerDuty.
  2. Navigate to the Integrations page.
  3. Under the PagerDuty section click Configure.
  4. Click Enable.
  5. Obtain the Integration Key.
    • Click Connect to use the simplified integration, which will generate the integration and allows you to obtain the Integration key. After this you will be redirected back to the same page.
    • Copy and paste your Integration key from the PagerDuty section (see above).
  6. Configure other settings and click Save.

How to Uninstall

To stop the Feroot project from creating triggers in PagerDuty, you will need to disable the PagerDuty integration in Feroot.

  1. Select the Feroot project that is configured to trigger PagerDuty incidents.
  2. Navigate to Integrations page.
  3. Under the PagerDuty section click Configure.
  4. Click Disable and then Save to stop creating triggers.

Learn How to Guard Your Web Applications Today

See Client-side Security in Action!