Skip to main content
Connect Cork to bring its compliance events, endpoints, inboxes and vulnerabilities into MSPortal. Setup belongs to MSP staff with Integrations settings and management access. Company users see only the security information their permissions and company scope allow.

Overview

Cork is a security and compliance platform that helps MSPs monitor their clients’ security posture. By integrating Cork with MSPortal.ai, you can:
  • View compliance events, vulnerabilities, and endpoints in a centralized dashboard
  • Track security metrics across all your managed clients
  • Add security findings to the Planner for remediation tracking
  • Include security data in client reports

Prerequisites

  • Active Cork account with API access
  • MSPortal.ai account with integration management permissions
  • Cork API key with read access

Part 1: Generate Cork API Key

Before connecting to MSPortal.ai, you need to create an API key in Cork.
1

Log into Cork

Access your Cork dashboard at app.corkinc.com or your Cork instance URL.
2

Navigate to API Settings

Go to Settings > API Keys in the Cork dashboard.
3

Create API Key

Click Create API Key or Add New Key.Configure the following:
A read-only API key is sufficient for MSPortal to sync your data. This follows the principle of least privilege.
4

Copy API Key

After creating the key, copy it immediately. Keep it out of shared documents and screenshots.
Store the API key securely! You may not be able to view it again after leaving this page. If you lose the key, you’ll need to create a new one.

Part 2: Connect Cork in MSPortal

The Cork connection page lists its tasks in the Setup guide: Connect, Import or match companies, Import devices and Review. See Connect and manage integrations for the tasks every connection shares.

Connect

1

Open the connection page

In MSPortal.ai, go to Settings > Integrations. On the Directory tab, find Cork and click Connect. To continue an existing Cork connection, open it from your active integrations instead.
2

Enter API Key

Paste your Cork API key into the API Key field.
Your API key is stored securely using Supabase Vault encryption. It is never exposed in logs or API responses.
3

Test the connection

Click Test connection to verify your credentials. A successful test does not create the connection.If the connection fails:
  • Verify you copied the full API key without extra spaces
  • Ensure the API key has not been revoked or expired
  • Check that your Cork account has API access enabled
4

Save and continue

Click Save and continue to create the connection. MSPortal starts a client sync in the background as soon as the connection is created; saving does not mean the clients have finished importing.

Import or match companies

This task opens Import or match Cork clients. Map Cork clients (organizations) to your MSPortal companies. This determines which data syncs to which company. Only data from matched clients syncs to MSPortal.
1

Load clients

If no clients appear yet, click Sync clients to fetch them from your Cork account.
The client sync runs in the background. Check back after a few minutes if clients don’t appear immediately, and check the sync result before creating a duplicate portal company.
2

Review suggestions

Open Suggested to review proposed matches, then click Accept on each correct one. Review N suggested matches opens Accept suggested matches, which lists every suggestion at 70% confidence or more with those at 90% or more already selected. Lower the Auto-select by confidence slider, as far as 70%, to select weaker suggestions too, untick any pair you want to check yourself, then select Apply N Matches.
3

Match the rest

For clients that weren’t matched, choose the correct MSPortal company in the row. To remove a match, use Remove match. Accepted matches and removals save immediately; wait for the result before leaving.
4

Import missing companies

If a Cork client doesn’t have a corresponding MSPortal company, click Import company in its row. Search for an existing company first to avoid duplicates, and check the resulting match.
Matching establishes company scope. It does not invite users or grant portal roles.

Import devices

Cork sends endpoint data that adds security information to your devices, so there are no staged devices to import. This task shows what has synced: Click Sync All Data to request a fresh import of compliance events, endpoints, inboxes and vulnerabilities for your matched clients. The sync runs in the background and the counts update as data arrives. Depending on your data volume, the first sync may take several minutes. A synced endpoint count is not proof that every endpoint is linked to an inventory device.

Review and finish setup

Open Review and select Finish setup once the required tasks are complete. Each match saves independently; finishing does not apply pending company links or wait for security imports.

What Gets Synced

Cork integration syncs the following data types to MSPortal:

Compliance Events

Security compliance findings from Cork, including:
  • Event type and description
  • Affected entity (device, inbox, or domain)
  • At-risk status
  • Resolution status
  • Creation date

Endpoints

Device and endpoint information:
  • Device name and hostname
  • Operating system type and version
  • IP addresses
  • Last seen timestamp

Inboxes

Email inbox data:
  • Inbox identifier
  • Associated user
  • Domain information

Vulnerabilities

Software vulnerability data:
  • CVE identifier
  • Affected software product and version
  • Vendor information
  • CVSS score (severity rating 0.0-10.0)
  • EPSS score (exploitation probability)
  • Cork priority (Critical, Accelerated, Routine)
  • Known exploited status

Synchronization Schedule

After initial setup, data syncs automatically:
You can trigger a manual sync at any time with Run sync in the connection header, or Sync All Data on Import devices. A sync request does not prove completion or a clean security assessment; check Sync activity for the result.

Managing Your Integration

Open the Cork connection from Settings > Integrations to manage it:

Checking or Replacing Your API Key

Open Connect to test the saved key or enter a replacement. Leave the masked value unchanged to keep the stored key. After testing a replacement, click Save changes and check the result. A test alone does not save a replacement. Verify the saved connection before you revoke the old key in Cork.

Troubleshooting

Frequently asked questions

No. After testing succeeds, choose Save and continue, then match clients.
Choosing a company or accepting a reviewed suggestion saves the match immediately. Importing a company and removing a match are saved actions too.
No. Review suggestions and the selected records before accepting them.
No. It requests a background sync from Cork; check the resulting datasets and errors.
No. Check the resulting datasets and freshness separately.
A test alone does not save the key. After testing a replacement, select Save changes and verify the saved connection before revoking the old key.
No. Check company matching, access, provider coverage and successful data synchronization first.

Security & Privacy

  • API Key Storage: Your Cork API key is encrypted using Supabase Vault and never exposed in logs or responses
  • Data Isolation: All synced data is tenant-isolated and only visible to your organization
  • Read-Only Access: MSPortal only requires read access to Cork data; it never modifies your Cork configuration

Next Steps

After setting up the Cork integration:

View Security Data

Explore compliance events, vulnerabilities, and endpoints

Read Cork Events

Review Cork compliance events per company

Read Vulnerabilities

Review vulnerabilities with CVE, CVSS, and priority

Add to Planner

Convert findings into actionable work items

Build Reports

Include security metrics in client reports

Other Integrations

Explore additional integration options
Related guides:

Need Help?

For assistance with the Cork integration, contact support@msportal.ai.