BCMLogic Next integrations

BCMLogic Next integrations.
Connect GRC to the systems your teams already run.

Identity, communication, ITSM, cloud, BI and vendor intelligence. Every connection is per-tenant, fully audited and revocable at any time.

Per-tenant isolationFull audit trailOne-click revocationData stays in the EU
BCMLogic Next connected to Microsoft Entra ID, Slack, Jira, Power BI, AWS, KNF, Microsoft Teams and ServiceNowEIDSKJIPBIAWSKNFMTSNBCMLogic NextREST API · webhooks

Why integrations

GRC only works when it lives where your people work

BCMLogic Next pushes risk alerts into Slack and Teams, opens tickets in Jira and ServiceNow, provisions users from Entra ID or Okta, and streams KRIs straight into Power BI – so compliance stops being a separate system and becomes part of your operating rhythm.

26
integrations in the catalog, including 2 in beta and 2 coming soon
7
categories, from SSO to vendor health data
1 API
the same one our own UI runs on
0
credentials shared between customers

Integration catalog

Seven areas, one platform

Search for the system you use or jump to a category. Integrations are switched on per tenant in the platform settings – no deployment work for your IT team.

Showing: 26

Identity & access

SSO and SCIM provisioning with Microsoft Entra ID, Okta, Google Workspace or any SAML 2.0 IdP. Users, groups and roles stay in sync with your directory – joiners, movers and leavers are handled automatically.

EIDMicrosoft Entra ID

SAML SSO plus SCIM 2.0 user and group provisioning.

Available

OKOkta

SAML 2.0 SSO with optional SCIM provisioning and group-to-role mapping.

Available

GGoogle Workspace

OIDC SSO with directory sync via SCIM. Access is removed automatically on offboarding.

Available

SAMLGeneric SAML 2.0

Bring your own IdP – configure entityId, ACS URL and X.509 certificate manually.

Available

Communication & collaboration

Risk alerts, vendor incident notifications and approval workflows delivered to Slack, Microsoft Teams or your own SMTP relay. KRI breaches and tabletop reminders reach the right channel, not another inbox.

SKSlack

Risk alerts, vendor incidents and approvals right in the channel.

Available

MTMicrosoft Teams

Adaptive cards for KRI breaches and tabletop exercise reminders.

Available

@SMTP / email relay

Custom SMTP for notifications – for organizations that control outbound mail.

Available

ITSM & ticketing

Push risks, control gaps and vendor findings as tickets to Jira, ServiceNow, Azure DevOps Boards or GitHub Issues – with bi-directional status sync, so remediation progress flows back into your risk register.

JIJira

Risks and control gaps as issues, with bi-directional status sync.

Beta

SNServiceNow

BCMLogic incidents mapped to ServiceNow incident and problem records.

Available

AZAzure DevOps Boards

Track control implementation as work items, auto-linked to the risk register.

Available

GHGitHub Issues

For tech-led teams: open issues directly from finding remediation.

Available

GRC & regulatory sources

Stay current without manual tracking: auto-imported EBA, ESMA and ENISA guidelines, the Polish KNF regulatory feed, pre-loaded ISO 22301/27001/31000 control libraries, and a maintained NIS2 ↔ DORA cross-walk mapped to your internal controls. More on compliance: DORA.

EBAEBA, ESMA, ENISA guidelines

Auto-import of guidelines and notifications on regulatory changes.

Available

KNFKNF positions & communications

Polish financial regulator feed – sector guidelines, communications, positions.

Available

ISOISO control library

ISO 22301, 27001 and 31000 control mappings, pre-loaded.

Available

NISNIS2 ↔ DORA cross-walk

NIS2 articles ↔ DORA RTS ↔ your internal controls, kept up to date.

Available

Cloud & infrastructure

Asset discovery across Azure, AWS and Google Cloud. Subscriptions, projects and resources map directly into your ICT registry, with region pinning enforced for EU data residency. Kubernetes inventory is coming soon.

AZMicrosoft Azure

Resource Graph sync – subscriptions and resources in your ICT registry.

Available

AWSAmazon Web Services

Account inventory via AWS Organizations, with critical assets auto-tagged in the ICT registry.

Available

GCGoogle Cloud Platform

Project hierarchy and asset inventory, with EU region pinning enforced.

Available

K8SKubernetes

Cluster, namespace and workload inventory for ICT mapping.

Coming soon

Data & BI

Native Power BI connector, Tableau Web Data Connector, or a read-only SQL endpoint for your own ETL. Your risk register, KRIs and vendor health metrics – in your BI stack, refreshed automatically.

PBIPower BI

Native connector with a live dataset for ERM dashboards, refreshed every 30 minutes.

Available

TTableau

Web Data Connector with extract refresh: risk register, KRIs, vendors.

Available

SQLRead-only SQL endpoint

Direct tenant-scoped read access for your own ETL or data warehouse.

Available

Vendor intelligence

Enrich your TPRM with external data: financial health and ownership structure from Dun & Bradstreet, security ratings from BitSight, breach detection via Have I Been Pwned. VendorHub Trust Center integration coming soon. See also vendor management.

DBDun & Bradstreet

Financial health, parent/subsidiary structure, beneficial owners.

Available

BRBitSight

External security ratings for vendor cyber posture, refreshed weekly.

Beta

HBHave I Been Pwned

Breach detection for vendor domains, with alerts on new exposures.

Available

VHVendorHub Trust Center

Questionnaire responses pulled directly from vendors.

Coming soon

How it works in practice

One event, five systems, zero retyping

Follow what happens when a risk indicator breaches its threshold. Click a step or play the whole scenario.






BCMLogic Next · KRI catalog
Failed logins to critical systems
Auto-updated from SIEM every hour

Threshold breached

warning threshold: 800

1,240
last 24 hours
+55%
above threshold
Illustrative visualization, sample data.

Security & control

Every connection under your control

Integrations in a GRC platform must meet the same standards you set for your own ICT providers. That’s why every one of them follows the same rules – whether you run SaaS on Microsoft Azure (Poland region) or an on-premise deployment.

Per-tenant isolation

Each integration’s configuration, tokens and data belong to your organization only. Nobody else uses them.

Full audit trail

Enabling, changes and every API call are logged. The log can be exported for your auditor or regulator.

Revocable at any time

Switch an integration off with one toggle in settings and revoke API tokens instantly.

No shared credentials

Least-privilege tokens, issued separately for each tenant and each connection.

Data stays in the EU

SaaS on Microsoft Azure in the Poland region, or on-premise. Cloud integrations respect region pinning.

ISO/IEC 27001 certified

BCMLogic services, both SaaS and on-premise, are certified to ISO/IEC 27001.

API & developer portal

Built API-first. Integrate anything.

Every capability in BCMLogic Next – risks, controls, vendors, BIA, incidents – is available through a documented REST API. The same API our own UI runs on.

Full coverage – everything you see in the platform, you can automate.

Per-tenant scoped tokens – least-privilege access, revocable instantly.

Complete audit trail – every API call logged, exportable for your regulator.

Webhooks – subscribe to risk, incident and vendor events in real time, e.g. open an incident automatically from a SIEM alert.

DataHub – a low-code ETL component for batch flows and historical data migration: CSV, XLS and database connectors, delivered as a Docker container.

Open the Developer Portal →

What you’ll find in the Developer Portal

OpenAPI specs
Full description of REST resources and operations.

Authentication
Tokens and permission scopes, step by step.

Sandbox environment
Test without touching production data.

Code samples
Ready-made snippets for common scenarios.

FAQ

BCMLogic Next integrations – frequently asked questions

Which systems does BCMLogic Next integrate with?

The catalog covers 26 integrations in 7 categories: identity and access (Microsoft Entra ID, Okta, Google Workspace, SAML 2.0), communication (Slack, Microsoft Teams, SMTP), ITSM (Jira, ServiceNow, Azure DevOps Boards, GitHub Issues), regulatory sources (EBA/ESMA/ENISA, KNF, ISO, NIS2 ↔ DORA cross-walk), cloud (Azure, AWS, Google Cloud), BI (Power BI, Tableau, SQL) and vendor intelligence (Dun & Bradstreet, BitSight, Have I Been Pwned). Other systems can connect through the REST API.

Does BCMLogic Next support SSO and Microsoft Entra ID (Azure AD)?

Yes. The platform supports SAML 2.0 and OIDC single sign-on plus SCIM 2.0 user and group provisioning. Ready-made integrations exist for Microsoft Entra ID, Okta and Google Workspace, and any other identity provider can be connected as generic SAML 2.0.

Can risks and remediation actions be pushed to Jira or ServiceNow?

Yes. Risks, control gaps and vendor findings can be sent as tickets to Jira (currently in beta), ServiceNow, Azure DevOps Boards or GitHub Issues. Status sync is bi-directional, so remediation progress flows back into the risk register.

How do I get risk data into Power BI or Tableau?

Power BI has a native connector with a dataset refreshed every 30 minutes; Tableau uses a Web Data Connector. Organizations with their own data warehouse can use a read-only SQL endpoint scoped to their tenant’s data.

Does BCMLogic Next have a public API?

Yes. The platform is built API-first: every capability available in the UI is exposed through a documented REST API. Webhooks cover real-time events and DataHub handles batch data exchange. Documentation, OpenAPI specs and a sandbox are available at developer.bcmlogic.com.

How are integrations secured?

Every connection is scoped to a single tenant, uses least-privilege tokens, is fully logged and can be revoked at any time. No credentials are shared between customers. BCMLogic services are certified to ISO/IEC 27001.

Does any data leave the European Union?

No. BCMLogic Next runs as SaaS on Microsoft Azure in the Poland region or on-premise on your own infrastructure. Cloud integrations respect region pinning, supporting data residency requirements.

Do integrations help with DORA and NIS2 compliance?

Yes, in several areas at once: cloud assets feed the ICT registry, the NIS2 ↔ DORA cross-walk links requirements to your controls, EBA, ENISA and KNF feeds flag regulatory changes, and the API call log serves as evidence for auditors. Integrations do not, however, replace risk analysis or management decisions.

The integration I need is missing. What next?

Request it – customer-requested integrations shape our roadmap. Most systems that have their own API can connect today through the BCMLogic Next REST API and webhooks.

Do integrations also work on-premise?

The REST API, webhooks and DataHub are available in both deployment models. Whether specific cloud-service integrations work in an on-premise installation depends on network connectivity in your infrastructure – we’ll confirm this during a call.

Next step

Missing an integration?

Tell us what you need. Customer-requested integrations shape our roadmap.