Credo AI

No entries match these filters. Clear filters

1. docs update Oct 3, 2026 · issue 093

   Credo AI adds Jira webhook integration for automated use-case creation and Splunk Shadow AI ingestion for AI activity discovery.

   • New integrationAdds Jira webhook integration to automatically create Credo AI use cases when Jira issues are created.
   • New integrationAdds Splunk Shadow AI ingestion to poll AI-usage/CASBCASBA Cloud Access Security Broker is a policy-enforcement proxy, on-premises or cloud-hosted, that sits between users and cloud services to provide visibility, compliance controls, and threat protection over SaaS and IaaS traffic.-style activity events from a Splunk index and forward them to Credo AI's Shadow AI Discovery surfaces.

   2 details in Everything

2. docs update Oct 3, 2026 · issue 093

   New Splunk poller forwards AI-usage events to the Research Preview POST /api/v2/{tenant}/shadow_ai/ai_events/bulk endpoint with checkpointing and retry logic.

   • Adds POST /api/v2/{tenant}/shadow_ai/ai_events/bulk backend endpoint (Research Preview) to ingest batches of AI-usage events into Credo AI's Shadow AI Discovery surface.
   • Adds a pull-based Splunk poller that queries a configurable SPLUNK_INDEX / SPLUNK_SOURCETYPE via Splunk's /services/search/jobs/export REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. and forwards results to the Shadow AI bulk endpoint on an interval.
   • New integrationAdds FIELD_MAP configuration to map Splunk field names (user_email, app_name, category, action, risk_score) to Credo AI's Shadow AI event schema.
   • Adds .env-based configuration via SPLUNK_HOST, SPLUNK_INDEX, and SPLUNK_SOURCETYPE to point the poller at any Splunk instance.
   • Provides per-batch checkpointing, transient-failure retry/backoff, client-side in-memory dedup, and permanent-rejection skip logic so dropped batches do not stall the polling cycle.

   5 details in Everything

3. api-docs-3efa27f93685 Oct 3, 2026 · issue 093

   Credo AI adds Custom Fields and Custom Field Types APIs for tenant-defined metadata on entities.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • Adds Custom Field Types API for defining and managing custom field schemas.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 detail in Everything

4. docs update Aug 30, 2026 · issue 059

   Credo AI adds JIRA webhook and ServiceNow Business Rule integrations to auto-create AI use cases from external ticketing systems.

   • Adds JIRA webhook integration to automatically create Credo AI use cases when Jira issues are created.
   • Adds ServiceNow integration that fires a server-side Business Rule on new record insertion into the AI intake table to create Credo AI use cases.

   2 details in Everything

5. docs update Aug 30, 2026 · issue 059

   Credo AI adds a native ServiceNow integration that auto-creates use cases from AI intake table inserts via a Business Rule.

   └──▷ HOW TO FIND IT
   Store Credo AI credentials in ServiceNow System Properties so the Business Rule can authenticate without exposing secrets in logs.
   📍Property Name: x_credo_ai.integration_url Type: String Value: https://<your-integration-service-base-url> Property Name: x_credo_ai.api_key Type: Password2 Value: <your-credo-ai-api-key> Property Name: x_credo_ai.tenant Type: String Value: <your-tenant-name>
   Wire up the ServiceNow Business Rule so every new AI intake record is automatically synced to Credo AI as a use case.
   📍Navigate to System Definition › Business Rules and create: Name: Send to Credo AI Table: x_ai_intake (your AI intake table) Advanced: true When to run: Insert — checked Then in the Script field, call CredoAIIntegration with your mapped columns: var credo = new CredoAIIntegration(); var useCase = credo.createUseCase({ name: current.getValue('u_ai_system_name'), description: current.getValue('u_description') }); if (!useCase) { current.setValue('u_credo_sync_status', 'failed'); current.update(); return; } current.setValue('u_credo_use_case_id', useCase.id); current.setValue('u_credo_sync_status', 'synced'); current.update();
   • Adds a native ServiceNow integration that triggers a Business Rule on AI intake table inserts and calls the Credo AI Integration Service to create a corresponding use case — no external server required.
   • Introduces three ServiceNow System Properties for credential storage: x_credo_ai.integration_url (String), x_credo_ai.api_key (Password2, encrypted at rest), and x_credo_ai.tenant (String).
   • Adds a CredoAIIntegration Script Include with a getToken() method (authenticates via POST /auth/token using X-API-Key and X-Tenant headers) and a createUseCase() method (posts to POST /use_cases with a Bearer tokenBearer tokenA credential that grants access to whoever presents it, without a separate proof of possession. Protecting the token matters because a stolen copy can be used by someone else.).
   • Adds two sync-tracking fields to the AI intake table: u_credo_use_case_id (String, populated with the returned use case ID on success) and u_credo_sync_status (Choice: pending / synced / failed).
   • All outbound API calls are logged natively in ServiceNow Application Logs, with no external JavaScript required.

   5 details in Everything