Onboard a Miro App to SSPM
Table of Contents
Expand all | Collapse all
-
-
- Allowed List of IP Addresses
-
- Begin Scanning a Bitbucket App
- Begin Scanning a Box App
- Begin Scanning ChatGPT Enterprise App
- Begin Scanning a Cisco Webex Teams App
- Begin Scanning a Confluence App
- Begin Scanning a Confluence Data Center App
- Begin Scanning a Dropbox App
- Begin Scanning a GitHub App
- Begin Scanning a Gmail App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a ShareFile App
- Begin Scanning a Slack Enterprise App
- Begin Scanning a Slack for Pro and Business App
- Begin Scanning a Workday App (Beta)
- Begin Scanning a Zendesk App
- Begin Scanning a Zoom App
- Reauthenticate to a Cloud App
- Verify Permissions on Cloud Apps
- Start Scanning a Cloud App
- Rescan a Managed Cloud App
- Delete Cloud Apps Managed by Data Security
- API Throttling
- Configure Classification Labels
- Microsoft Labeling for Office 365
- Google Drive Labeling
- Configure Phishing Analysis
- Configure WildFire Analysis
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- Filter Incidents
- Configure Slack Notification Alerts on Data Security
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- Customize the Incident Categories
- Close Incidents
- Download Assets for Incidents
- View Asset Snippets for Incidents
- Analyze Inherited Exposure
- Email Asset Owners
- Modify Incident Status
-
-
-
- What’s SaaS Security Inline?
- Navigate To SaaS Security Inline
- SaaS Visibility for NGFW
- SaaS Visibility and Controls for NGFW
- SaaS Visibility for Prisma Access
- SaaS Visibility and Controls for Panorama Managed Prisma Access
- SaaS Visibility and Controls for Cloud Managed Prisma Access
- Activate SaaS Security Inline for NGFW
- Activate SaaS Security Inline for VM-Series Firewalls with Software NGFW Credits
- Activate SaaS Security Inline for Prisma Access
- Connect SaaS Security Inline and Strata Logging Service
- Integrate with Azure Active Directory
-
-
- SaaS Policy Rule Recommendations
- App-ID Cloud Engine
- Guidelines for SaaS Policy Rule Recommendations
- Predefined SaaS Policy Rule Recommendations
- Apply Predefined SaaS Policy Rule Recommendations
- Create SaaS Policy Rule Recommendations
- Delete SaaS Policy Rule Recommendations
- Enable SaaS Policy Rule Recommendations
- Modify Active SaaS Policy Rule Recommendations
- Monitor SaaS Policy Rule Recommendations
-
- Enable Automatic Updates for SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Import New SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Update Imported SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Remove Deleted SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Manage Enforcement of Rule Recommendations on NGFW
- Manage Enforcement of Rule Recommendations on Panorama Managed Prisma Access
- Change Risk Score for Discovered SaaS Apps
-
-
-
-
- Onboarding Overview for Supported SaaS Apps
- Onboard an Aha.io App to SSPM
- Onboard an Alteryx Designer Cloud App to SSPM
- Onboard an Aptible App to SSPM
- Onboard an ArcGIS App to SSPM
- Onboard an Articulate Global App to SSPM
- Onboard an Atlassian App to SSPM
- Onboard a BambooHR App to SSPM
- Onboard a Basecamp App to SSPM
- Onboard a Bitbucket App to SSPM
- Onboard a BlueJeans App to SSPM
- Onboard a Box App to SSPM
- Onboard a Bright Security App to SSPM
- Onboard a Celonis App to SSPM
- Onboard a Cisco Meraki App to SSPM
- Onboard a ClickUp App to SSPM
- Onboard a Confluence App to SSPM
- Onboard a Contentful App to SSPM
- Onboard a Convo App to SSPM
- Onboard a Couchbase App to SSPM
- Onboard a Coveo App to SSPM
- Onboard a Crowdin Enterprise App to SSPM
- Onboard a Customer.io App to SSPM
- Onboard a Databricks App to SSPM
- Onboard a Datadog App to SSPM
- Onboard a DocHub App to SSPM
- Onboard a DocuSign App to SSPM
- Onboard an Envoy App to SSPM
- Onboard an Expiration Reminder App to SSPM
- Onboard a Gainsight PX App to SSPM
- Onboard a GitHub Enterprise App to SSPM
- Onboard a GitLab App to SSPM
- Onboard a Google Analytics App to SSPM
- Onboard a Google Workspace App to SSPM
- Onboard a GoTo Meeting App to SSPM
- Onboard a Grammarly App to SSPM
- Onboard a Harness App to SSPM
- Onboard a Hellonext App to SSPM
- Onboard an IDrive App to SSPM
- Onboard an Intercom App to SSPM
- Onboard a Jira App to SSPM
- Onboard a Kanbanize App to SSPM
- Onboard a Kanban Tool App to SSPM
- Onboard a Kustomer App to SSPM
- Onboard a Lokalise App to SSPM
- Onboard a Microsoft Azure AD App to SSPM
- Onboard a Microsoft Outlook App to SSPM
- Onboard a Microsoft Power BI App to SSPM
- Onboard a Miro App to SSPM
- Onboard a monday.com App to SSPM
- Onboard a MongoDB Atlas App to SSPM
- Onboard a MuleSoft App to SSPM
- Onboard a Mural App to SSPM
- Onboard an Office 365 App to SSPM
- Onboard an Okta App to SSPM
- Onboard a PagerDuty App to SSPM
- Onboard a RingCentral App to SSPM
- Onboard a Salesforce App to SSPM
- Onboard an SAP Ariba App to SSPM
- Onboard a ServiceNow App to SSPM
- Onboard a Slack Enterprise App to SSPM
- Onboard a Snowflake App to SSPM
- Onboard a SparkPost App to SSPM
- Onboard a Tableau Cloud App to SSPM
- Onboard a Webex App to SSPM
- Onboard a Workday App to SSPM
- Onboard a Wrike App to SSPM
- Onboard a YouTrack App to SSPM
- Onboard a Zendesk App to SSPM
- Onboard a Zoom App to SSPM
- Onboarding an App Using Azure AD Credentials
- Onboarding an App Using Okta Credentials
- Register an Azure AD Client Application
- View the Health Status of Application Scans
- Delete SaaS Apps Managed by SSPM
Onboard a Miro App to SSPM
Connect a Miro instance to SSPM to detect posture risks.
For SSPM to detect posture risks in your Miro instance, you must onboard your Miro
instance to SSPM. Through the onboarding process, SSPM connects to a Miro API and,
through the API, scans your Miro instance for misconfigured settings. If there are
misconfigured settings, SSPM suggests a remediation action based on best
practices.
SSPM gets access to your Miro instance through OAuth 2.0 authorization. To enable
OAuth 2.0 authorization, you first create an OAuth 2.0 application in Miro before
onboarding your Miro instance in SSPM. During the onboarding process, you are
prompted to log in to Miro and to grant SSPM the access it requires.
To onboard your Miro instance, you complete the following actions:
Collect Information for Connecting to Your Miro Instance
To access your Miro instance, SSPM requires the following application
credentials. You will create the OAuth 2.0 application and provide its
credentials to SSPM during the onboarding process.
Item | Description |
---|---|
Client ID | SSPM will access a Miro API through an OAuth 2.0 application that you create. Miro generates the Client ID to uniquely identify this application. |
Client Secret | SSPM will access the Miro API through an OAuth 2.0 application that you create. Miro generates the Client Secret, which SSPM uses to authenticate to this application. |
As you complete the following steps, make note of the values of the items
described in the preceding table. You will need to enter these values during
onboarding to enable SSPM to access your Miro instance.
- From SSPM, get a redirect URI. You will specify this redirect URI in the OAuth 2.0 application that you will create in Miro. To get this information, you will begin the onboarding process in SSPM, but you will not complete the process.
- From the Add Application page in SSPM ( Posture SecurityApplicationsAdd Application), click the Miro tile.
- Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.
- Log in with Credentials.A connection page for onboarding a Miro instance is displayed. The Redirect URL field displays the redirect URL value.
- Copy the URL and paste it into a text file. Do not continue to the next step unless you have copied the redirect URL. You will need to specify this URL later when you are configuring your OAuth 2.0 application.
- Because you will not be completing the onboarding process until after you have created your OAuth 2.0 application and gathered the necessary configuration information, return to the Apps Onboarding page.
Identify the administrator account that you will use to create your OAuth 2.0 application.(Required Permissions) The OAuth 2.0 application must be created by a Miro administrator assigned to the Company Admin role.Create your OAuth 2.0 application.- Open a web browser and go to the Miro login page at miro.com/login/.
- Log in to the Company Admin account that you identified earlier.
- Locate your profile icon and select <profile-icon> Settings.
- On your Profile settings page, select Your appsCreate new app.
- In the Create new app dialog:
- Specify a name and developer team for your app.
- Select Expire user authorization token.
- Create app.
Miro displays a page for configuring your app. - The configuration page for your app displays the app credentials
(Client ID and Client Secret). Copy these credentials and paste them
into a text file.Do not continue to the next step unless you have copied the Client ID and Client Secret. You must provide this information to SSPM during the onboarding process.
- On the configuration page for your app, locate the
Redirect URI for OAuth 2.0 section.
Add the redirect URI that you obtained
from SSPM to your OAuth 2.0 application.Double check that the Expire user authorization token option is selected. You cannot change this option setting here, but should have made this selection in the Create new app dialog.
- On the configuration page for your app, locate the
Permissions section. Select the following
scopes for your app:
- boards:read
- organizations:teams:read
- Install app and get OAuth token.
Connect SSPM to Your Miro Instance
By adding a Miro app in SSPM, you enable SSPM to connect to your Miro instance.- From the Add Application page ( Posture SecurityApplicationsAdd Application), click the Miro tile.Under posture security instances, Add Instance or, if there is already an instance configured, Add New instance.Log in with Credentials.Enter the application credentials (Client ID and Client Secret) and Connect.SSPM redirects you to the Miro login page.Log in to Miro as a Miro administrator assigned to the Company Admin role.Miro displays a consent form that details the access permissions that SSPM requires.Review the consent form and allow access.After you have granted SPPM the access it requires, SPPM will use the Company Admin permissions to scan for misconfigurations across all of your Miro teams.