Integrations Standards

TLP:AMBER - Limited disclosure, recipients can only spread this on a need-to-know basis within their organization and its clients. Recipients may share TLP:AMBER information with members of their own organization and its clients, but only on a need-to-know basis to protect their organization and its clients and prevent further harm 

Overview

Integrations in Rewst are the backbone of the platform, allowing you to create repeatable automations to platforms with existing API actions or custom APIs. It is therefore critical that all integrations are configured properly and mapped to all clients in the rewst organization, and that workflows that utilize specific integrations account for the potential of a misconfigured organization (especially if the trigger is set to run on all current and future orgs).

 

Integration Best Practices

1. Ensure all required integrations have all required fields filled and validated

  • After adding your relevant integrations, ensure each one has been configured fully and is not throwing any errors.
  • If an integration has issues, the ROC team should be contacted for assistance (unless it is a custom integration).
    • If an integration has issues and will not be used, it should be removed. 

2. All Integrations should have all companies mapped

  • Most integrations will contain a mapping table to match organizations configured in the integration with organizations configured in Rewst. This allows workflows to use the correct organization information when making API calls from an execution in a subtenant.
  • Ensure all organizations in Rewst are mapped to the corresponding organization from the integration, if applicable

3. Only used integrations should be enabled

  • Do not enable integrations for platforms you do not currently intend to use.
  • Regularly review usage of integrations and remove any ones not in use.

4. Regularly review integrations for errors

  • On the Rewst homepage, review the "Integrations Needing Attention" on a regular basis.
  • Address any integrations in the list and remove any that are not in use.