Skip to content
SAP, DATEV and Dynamics experts

IT & API security

Interfaces carry exactly the data a company least wants to lose: customer records, prices, orders, invoices. This category covers securing those connections — authentication and key management, permissions following the principle of least privilege, encryption in transit, rate limiting, logging and reviewing access. Added to this are organisational questions: who may create credentials, how are they revoked when service providers change, and what does an emergency procedure look like on suspicion of compromise? We also address requirements from data protection and security regulation and describe test steps that can be repeated on a regular schedule. We additionally cover how to log interface access without unnecessarily storing personal data.

NIS2: Hardening ERP-to-Shop InterfacesMaking the API between shop and ERP compliant with NIS2Online ShopOrder and customer dataSecurity GatewayOAuth 2.0 + OpenID ConnectmTLS - end-to-end TLSERP / SAPInventory systemThe five hardening steps at a glance1InventoryMap everyinterface2EncryptionTLS 1.3, endto end3AuthenticationOAuth 2.0,mTLS, OIDC4MonitoringLogs and 24hreport to BSI5Supply chainProviderevidence29,500companies underBSI oversight (BSI)10m Euromax. fine, alternatively2% of global turnover24 / 72 hinitial and detailedreport to BSI289.2bn euro in annual damage to the German economy from cyberattacks and data theft (Bitkom).Audit, hardening, documentation and NIS2-compliant API development from one partner.
IT & API security Jul 8, 2026

NIS2 and API Security: Hardening ERP Interfaces

NIS2 has applied since December 2025: inventory ERP-to-shop interfaces, encrypt them end-to-end via TLS and secure them with OAuth 2.0, OpenID Connect and mTLS.

13 min read
OAuth 2.0: bound, short-lived tokens for ERP APIsClient credentials flow, mTLS/DPoP and scope minimization instead of static keysShop clientMiddleware / connectorAuthorization ServerToken endpointClient credentials flowERP / Resource ServerSAP, Dynamics, ERP1. Request token3. Present token2. Issue access tokenAccess Tokenscope: orders:read (least privilege)exp: 5 minutes, short-livedcnf: mTLS certificate / DPoPsender-constrained (RFC 9700)Static API key vs. OAuth 2.0 tokenStatic API keyLifetime: unlimitedRevoke: only global rotationBinding: none, plain bearerScope: usually full accessOAuth 2.0 tokenLifetime: minutes, rotatingRevoke: per tokenBinding: mTLS or DPoPScope: narrow, per task
IT & API security May 11, 2026

OAuth 2.0 and Token Security for ERP Interfaces

Many ERP-to-shop APIs still run on static keys. How the client credentials flow, mTLS, DPoP, short token lifetimes and scope minimization harden the API.

13 min read