> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/updates/product-updates/january-2025.md). # January 2025 ## Log Analysis We’ve added a Log Analysis feature that lets you upload historical conversation logs from your AI application and run our detectors on them retroactively. The feature searches for the same vulnerabilities as our probes (context leakage, jailbreaks, and others) while scanning existing conversations instead of actively provoking attacks. Upload your logs, choose the detectors you need, and Log Analysis returns key metrics: messages, exploit attempts, and vulnerabilities detected, and plots them so you can easily spot spikes.\ Granular filters and one-click drill-downs let you quickly inspect every user’s interaction with your application. ## Keycloak Authentication We’ve migrated our authentication system to Keycloak. This upgrade brings built-in multi-factor authentication and stronger OAuth2/OIDC security. It also enables us to add quick sign-in with Google, Microsoft, and other identity providers in the future, reducing login friction across our platform. ## Multi-Factor Authentication (MFA) We’ve added Multi-Factor Authentication (MFA) to the platform, bringing an extra layer of account security at sign-in.\ Organization owners can make MFA mandatory for every user in their SplxAI Platform organization, and when it isn’t required, individual users can still enable MFA for their own accounts. ## Improvements & Tweaks In Target Settings, you can now mark any HTTP header as Sensitive, hiding its value from view and preventing it from being logged or shared. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.probe.splx.ai/updates/product-updates/january-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.