Operate integrations without creating a shadow perimeter.

01 / Credentials

Issue a key for one system and one purpose.

• Name the owning system and environment.
• Select only the scopes required for its documented flow.
• Copy the plaintext once into that system’s secret manager.
• Set an expiry when the integration can support scheduled rotation.
• Rotate immediately after suspected disclosure; revoke retired keys.

02 / Event delivery

Acknowledge quickly, process safely.

Verify the timestamp and HMAC against the exact raw request body, deduplicate on x-forge-delivery, enqueue internal work, and return a 2xx response. Revolution Road retries non-2xx and network failures with exponential backoff before dead-lettering.

03 / Data exchange

Validate before import; reconcile after export.

Use asset tags as the import identity. Review row-level validation output before retrying. Exports are UTF-8 CSV and protect formula-like leading characters for safer spreadsheet use.

04 / Operations

Watch traffic and delivery together.

• Alert on sustained API error-rate or request-volume spikes.
• Track p95 latency and remaining rate-limit capacity.
• Investigate dead-letter deliveries and repeated endpoint timeouts.
• Retain request IDs in ERP and connector logs.
• Never log bearer keys, signing secrets, or webhook bodies containing sensitive data.

05 / Enterprise readiness

Activate SSO and SCIM only with a named provider.

The database contracts are disabled by default. Complete identity-provider metadata exchange, attribute mapping, domain verification, token rotation, and deprovisioning acceptance tests before enabling federation.