> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/integrations/shared-signals-framework-ssf-and-ssf-receivers.md). # Shared Signals Framework (SSF) and SSF Receivers ### What is the Shared Signals Framework (SSF)? Cisco Identity Intelligence can ingest signals from security products and platforms that have adopted Shared Signals Framework through an SSF receiver that you configure in the product. These external detections and risk signals are then surfaced in CII to support centralized visibility, investigation, and identity threat insights. The Shared Signals Framework (SSF) is an open, standardized approach for exchanging identity and security signals between systems. It enables a signal provider (for example, a security platform) to publish events and a signal consumer (such as Identity Intelligence) to receive and act on those events in near real time. ### What is an SSF receiver in Identity Intelligence? An SSF receiver is the integration component in Intelligence that allows it to connect to an SSF-adopting provider and ingest the provider’s signals. Once configured, the receiver continuously brings external signals into Identity Intelligence so they can be used to drive detections, checks, and investigation workflows. ### Benefits of using SSF in Identity Intelligence * Near real-time signal ingestion to shorten time to detect and respond. * Centralized visibility by aggregating signals from multiple providers in one console. * More actionable detections by enriching incoming signals with identity context and user population data. * Standards-based integrations that reduce custom integration effort and make it easier to add new signal sources over time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.oort.io/integrations/shared-signals-framework-ssf-and-ssf-receivers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.