Connect Breach Secure Now to MSPortal.ai to sync security awareness training, phishing, and dark web breach metrics
This guide walks you through connecting Breach Secure Now (BSN) to MSPortal.ai. Setup is for MSP staff with integration management permission. On the BSN connection page, the Setup guide has three tasks: Connect, Import or match companies and Review.
Part 1: Enable the Integration in Breach Secure Now
Before connecting, you need your Partner Integration Key from Breach Secure Now.
1
Log into the Breach Secure Now Partner Portal
Sign in to your Breach Secure Now (PII Protect) partner portal with a partner administrator account.
2
Open the Integrations Section
Navigate to the integrations area of your partner configuration and locate MSPortal in the list of available integrations.
3
Enable MSPortal
Enable the MSPortal integration for your partner account.
If MSPortal does not appear in your integrations list, contact Breach Secure Now support and ask them to enable the MSPortal API integration for your partner account.
4
Copy Your Partner Integration Key
Copy the Partner Integration Key, the secret key generated when the integration is enabled. This is the only value you enter in MSPortal.
You do not need your Partner ID. MSPortal identifies your partner account from the Partner Integration Key automatically.
Treat the Partner Integration Key like a password. Anyone with the key can read your client and user training data.
In MSPortal.ai, go to Settings > Integrations, choose Directory, find Breach Secure Now, and choose Connect. To maintain an existing connection, open it from your active integrations instead.
2
Enter Your Partner Integration Key
Fill in the connection fields:
Field
Value
Partner integration key
The integration key from the BSN portal
API base URL
Pre-filled with https://api.pii-protect.com/securedapiaccess. Leave the default unless Breach Secure Now has given you a different endpoint.
3
Test Connection
Choose Test connection to verify your key.When the test passes, a confirmation shows your partner name and a client count. This confirms MSPortal matched your key to the right partner account.
The test reads only the first five clients, so the count tops out at 5. Your full client list appears on Import or match companies.
If the connection fails:
Verify the Partner Integration Key was copied in full, without extra spaces
Confirm the MSPortal integration is enabled for your partner account in the BSN portal
If you see “That Partner Integration Key was not recognized by Breach Secure Now,” return to Part 1, enable MSPortal for that partner account, copy the key again, then test again
4
Save the connection
Once the test passes, choose Save and continue. This saves the connection and starts client discovery in the background. A successful test alone does not save anything.
Your credentials are stored with encryption and are never exposed in logs or API responses.
Map your Breach Secure Now clients to MSPortal companies. This determines which data syncs to which company.
1
Sync Your Clients
Open Import or match companies. If no clients have synced yet, choose Sync clients to pull your client list from Breach Secure Now. The sync usually takes less than a minute, and new clients appear as they arrive.
2
Match Clients
For each BSN client, accept the suggested company or choose the correct MSPortal company. Accept strong matches accepts every suggestion at 90% confidence or more after you review them. Ignore hides a BSN client you do not want to map, and you can restore it later.
3
Import Missing Companies
If a BSN client does not have a corresponding MSPortal company yet, use Import company on its row. MSPortal creates the company right away and matches it to the BSN client. Check for an existing company first to avoid duplicates.
4
Check the Saved Matches
Each accepted or chosen match saves immediately and starts a user training sync for that client. Removing a saved match also takes effect immediately.
Only data from mapped clients syncs to MSPortal. Map at least one client before you finish setup.
Use Overview and Sync activity to check the connection and the results of each sync. Run sync starts a sync in the background; the first sync can take several minutes, depending on how many clients and users you have.
2
Finish Setup
Open Review and choose Finish setup. Finishing setup does not wait for the background sync, which keeps running after you leave.
User-level metrics stay empty until the first user sync finishes. Missing values, zero counts and a connected status do not prove that everyone is trained or free of exposure. Check the company match and when the data last synced.
After the initial setup, data syncs automatically once per day. Clients sync first, followed by user training data.
You can trigger a manual sync at any time: open the Breach Secure Now connection from Settings > Integrations and choose Run sync. Check Sync activity for the result before relying on new data.
After setup, open the Breach Secure Now connection from Settings > Integrations:
Action
Description
Connect
Test the saved key without re-entering it, or enter a new Partner Integration Key and choose Save changes to replace it. Testing alone does not save it. Leave the masked key unchanged to keep it. Changing the API base URL requires entering the key again.
Import or match companies
Match clients you onboarded in Breach Secure Now since the last visit
Run sync
Start a manual data refresh
Disconnect…
Under More actions. Removes the connection, synced BSN data, and stored credentials. It does not revoke the key in Breach Secure Now.
Re-copy the Partner Integration Key from the BSN portal, checking for extra spaces
”That Partner Integration Key was not recognized”
Confirm the key was copied in full, and that the MSPortal integration is enabled for your partner account in the Breach Secure Now portal, then test again
”Breach Secure Now returned a web page instead of API data”
The API base URL points at the BSN portal website. Set it back to https://api.pii-protect.com/securedapiaccess
”The Breach Secure Now API base URL must be a pii-protect.com address”
Only pii-protect.com addresses are accepted. Restore the default API base URL
Setup reports a service configuration problem
Ask MSPortal support to investigate the reported error; a new Partner ID is not required
No clients appear on Import or match companies
Choose Sync clients, wait a moment for the background sync, then check the list again
No user metrics
Confirm the client is matched, run a sync, and check its result in Sync activity
A client’s data is missing
Confirm the client is mapped to a company; only mapped clients sync
Counts still look old
Check Sync activity after the background work finishes; the sync started message only confirms the request