Skip to content

Not open yet. Registrations will open soon.

All applications

SOC

Your logs in one place, alerts when something is wrong, a case file for every incident, and a vault for passwords and access to servers.

In preparation Create an accountAlso for

SOC gathers the logs of the whole organization: those of Windows and Linux machines, through a small program installed with a single command, and those of your own applications, through an API or through a log type that you describe yourself, without writing any code. A single search goes through all of them, with a simple language ("host:web01 AND level>=warning"), per-minute charts and the list of the most frequent values.

Rules watch the stream: one event is enough, or too many failures from the same address, or a machine that has gone quiet. Twenty-four rules are included, each tied to a MITRE ATT&CK technique. An alert groups similar events instead of repeating itself; you take it on, annotate it, open it as a case, and email, a webhook, Slack or Teams notify the right person without drowning them.

The collector only reads: it opens no port, receives no order from the server and reads only what the machine's administrator has allowed it to read. It keeps its batches on disk when the network goes down and resends them afterwards, without duplicates. Your AI agents can query the logs and handle alerts through the MCP endpoint, without ever deleting anything. SOC searches and alerts: it is neither an antivirus nor an automatic response tool.

The vault (Vault module) keeps the organization's passwords, authentication codes (TOTP), SSH keys and certificates on the same site, in vaults shared by person. For servers, an SSH and RDP gateway opens the session in the browser without ever handing over the credential, records it (encrypted, announced from the first line, replayable only by the administrators) and lets it be observed live or cut. An Android app computes one-time codes without a network. The vault follows the SOC's license and rights.

SOC is in preparation. It will join the Prophetix subscription catalogue when it is released.

Every feature of SOC

147 features in 23 areas

Dashboard

  • Shows the alerts to handle, updated every 30 seconds.
  • Plots the number of events received over 24 hours.
  • Flags silent collectors: machine switched off, network down, service stopped, or collector neutralized by an intruder.
  • Suggests first steps: install a collector, create an API key, describe your logs, see the rules, set up notifications.

Windows and Linux collectors

  • A standalone file, with nothing to install beforehand, installed by a command to paste that is written on screen with the address of your server.
  • Collectors for Windows and Linux, in x64 and ARM64; .deb package for Debian and Ubuntu.
  • Reads the Windows Event Log: Security, System, Application, PowerShell, Defender and Sysmon, with the chosen event IDs.
  • Reads journald on Linux, as well as log files and syslog depending on the profile.
  • Enrolls each machine with a limited-use ticket, shown once and valid for a few days.
  • Checks the SHA-256 fingerprint of the download before installing.
  • Keeps its batches on disk when the network goes down and resends them afterwards, without duplicates.
  • Signs every submission; a machine revoked from the console stops by itself.
  • Tracks the state of each collector: pending, online, silent, revoked.
  • Chooses what each machine reads with collection profiles, which can be checked before use, with a default profile per system.
  • Applies the intersection of the profile and a local allowlist that only the machine's administrator can write.
  • Receives no order from the server, opens no port and executes nothing remotely.

Your own logs

  • Sends events through the API with a key, as JSON, NDJSON or raw lines, with optional gzip compression.
  • Watches a log file with the collector.
  • Describes a log type in the screen without writing code: free text, regular expression, JSON, key-value pairs, CEF or syslog.
  • Indicates which part of the line becomes the time, the level, the machine, the account, the source or destination address, the message, and keeps the rest as free fields.
  • Tries the type on a line before saving it.
  • Provides a sample template for nginx access logs.
  • Gives sending examples with Fluent Bit, Vector and rsyslog.
  • Forces a stream onto a key if needed, handy for a sender you do not control.

Search

  • Searches all events with a one-line language, for example host:web* AND level>=warning -user:svc-*.
  • Displays per-minute charts and the list of the most frequent values of a field.
  • Saves its searches and shares them with the team.
  • Follows events as they arrive live.
  • Exports the result as CSV or NDJSON.
  • Loads further results on demand, with built-in help on fields and operators.
  • Displays all times in UTC.

Detection rules

  • 24 rules included for Windows, Linux and common services, each tied to a MITRE ATT&CK technique.
  • Detects by match (one event is enough), by threshold (too many failures from the same address or account, distinct values) or by absence (a machine that has gone quiet).
  • Covers, for example, cleared log, burst of failed logins, password spraying, account created, addition to an administration group, new service, SSH brute force, root login.
  • Creates your own rules with window, threshold, severity, silence period after an alert and evaluation frequency.
  • Writes for each rule a handling tip in Markdown, shown on the alert.
  • Tries a rule on the last 24 hours before enabling it.
  • Keeps watchlists, for example of bad addresses, referenced in a search or a rule.
  • Chooses the notification channels of each rule.

Alerts and cases

  • Groups similar events into a single alert instead of repeating it.
  • Takes on, assigns, resolves an alert or classifies it as a false positive.
  • Reads what happened, the timeline, what to do and sample events, and opens all the events of the alert in the search.
  • Adds notes to an alert.
  • Opens a numbered case SOC-n with one or several alerts, a title, a severity and an owner.
  • Moves the case forward: open, in progress, contained, closed, with a timeline and notes.
  • Closes the case with an outcome: true positive, false positive, test or exercise, other.
  • Keeps an audit log of the team's actions, filterable by author and by type.

Notifications

  • Notifies by email, HMAC-SHA256 signed webhook, Slack or Microsoft Teams.
  • Sets the minimum severity of each channel.
  • Tries a channel before relying on it.
  • Goes through a queue that retries failed sends; you can also resend by hand.
  • Displays the latest notifications with their state and the last error.
  • Refuses internal addresses and http:// so that it cannot be used to probe your network.

Access, API and AI agents

  • Four roles: reader, analyst, detection engineer, administrator.
  • The first person of an organization and any Prophetix owner or administrator is an administrator; each organization sees only its own data.
  • An expired license puts SOC in read-only mode but does not interrupt the reception of logs.
  • REST API with keys (ingestion, read, write): send events, search, list alerts, cases, collectors and rules, handle an alert.
  • Documents the API at /api/docs.
  • Limits the rate to 600 requests per minute per key and 60,000 events per minute per organization.
  • Offers an MCP endpoint for your AI agents: search, count, read alerts and cases, change a status, annotate, open a case.
  • No MCP tool deletes anything, sends a message or runs a command; the agent is warned that the text of a log comes from outside.

Retention, import and export

  • Sets the retention period of the logs (30 days by default, 400 at most).
  • Shows the space used and recounts it exactly.
  • Exports the events of a query as CSV or NDJSON.
  • Exports the configuration (rules, lists, log types, profiles) as a JSON file with no secrets, readable with any tool.
  • Imports this package into another organization, replacing or not what exists under the same name.

On your devices

  • Web: the complete application, with single sign-on and data on the server.
  • Windows and Linux: the collector, a Windows service or systemd, which keeps reading the logs without a connection.
  • No desktop application and no Android application: a SOC lives on logs coming from several machines. On a phone, alerts arrive by email or webhook and the web page adapts to the screen.

Good to know

  • SOC searches and alerts: it is neither an antivirus nor an automatic response tool.
  • No Sigma engine and no behavioral detection.
  • Tried end to end on real Linux (Ubuntu) and on Windows ARM64; the Windows installation as administrator and the x64 collectors have not been run.
  • The server is not online yet; real sending of email, Slack and Teams messages and load have not been tried.
  • A single database on one node: comfortable up to a few million events per organization.
  • Not yet connected to the platform's storage quotas; retention and an ingestion limit bound the volume.
  • Not available yet: native notification of critical alerts on the on-call person's phone, and acknowledging an alert with one gesture.

Vaults, folders and search

  • Keeps an organization's secrets in vaults, themselves organized into nested folders.
  • Creates, renames, moves and deletes vaults and folders; a folder that is not empty cannot be deleted.
  • Searches titles, usernames, addresses, hosts, vaults and folders; several words add up.
  • Filters by favorites, by entries about to expire, or by vault or folder with its subfolders.
  • Appears in three columns (tree, list, detail) on a large screen, and in one pane at a time on a phone.
  • Follows the system's light or dark theme.
  • Lets you choose the organization at sign-in when you belong to several, and switch between them.

Entries and secrets

  • Handles eight entry types: password, remote desktop, SSH connection, database, API key, secure note, bank card, identity.
  • Adds notes, custom fields, an expiry date, a favorite flag and a one-time code to each entry.
  • Generates a password and measures its strength with a gauge.
  • Moves an entry between folders, or between vaults with re-encryption.
  • Keeps the old password in the entry's history at every change.
  • Never shows a secret in a list or on the detail page: it is displayed for thirty seconds or copied, with the clipboard cleared after thirty seconds.
  • Keeps a secret left blank when editing, instead of erasing it.
  • Encrypts passwords, SSH keys and certificates in the database; each vault has its own key.

One-time codes and Authenticator

  • Calculates TOTP codes on the server and displays them with a countdown, copyable in one click.
  • Provides an Authenticator page: adding a code by otpauth address or by settings, removing it, copying it.
  • Stores each code as a vault entry, by default in the personal "Authenticator" vault.
  • Calculates SHA-1, SHA-256 or SHA-512 codes, of 6 to 8 digits.
  • Offers an Android authenticator app (written, not yet published): codes displayed without a network, synchronized with the vault.
  • Adds a code on the phone by QR code, by pasted address, by Google Authenticator export or by typing in the key.
  • Approves Prophetix sign-ins with one touch using this app: the notification opens the request and you tap the right number out of three.
  • Locks the app with biometrics or the phone's code, and can back up the encrypted codes to a private Google Drive space.

Sharing and rights

  • Shares a vault by person, with read, read-write or administration rights.
  • Reserves vault management to its owner and its administrators.
  • Keeps organizations separate: a member of another organization sees nothing.
  • Switches to view-only when the organization has no license: you can read, but change nothing.

Access journal and history

  • Logs every access: who, what, when, from which address, which device and which session.
  • Keeps only the name of the field viewed in the journal, never its value.
  • Shows each person their own actions, the administrators of a vault all those in their vault, and those of the organization the whole organization.
  • Shows each entry's activity in a tab of its detail page.
  • Filters the history by period, vault, member, action and field, or by secret fields only.
  • Presents figures, a daily curve and the ranking of the most active members and entries.
  • Exports the history as CSV or JSON, or prints it as PDF, and records each export in the history.

SSH gateway and privileged access

  • Makes the server the SSH client: the person opens the session in their browser without ever seeing the credential.
  • Reserves an entry for the gateway: the password and key are never handed over, displayed or copied.
  • Records the session (what is displayed, not the keystrokes) in an encrypted file and announces the recording from the first line.
  • Replays a recording, with play, speed and download, checking its integrity; replay is reserved to the vault's administrators and logged.
  • Allows a running session to be cut, by the owner, the vault's administrators and the organization's administrators.
  • Remembers the host key on first connection and refuses a different key.
  • Chooses a recording policy per vault: optional, mandatory or disabled.
  • Opens PowerShell or Windows PowerShell directly over SSH from the entry.
  • Limits session duration, inactivity, the number of sessions per person and the retention period.

Recorded remote desktop (RDP)

  • Opens a remote desktop in the browser: the server holds the RDP connection and the browser displays.
  • Draws a strip below the desktop with the name, email, organization, "session recorded" and the UTC time.
  • Includes this strip in the recording: the replay carries the identity and the time.
  • Closes the clipboard, files, printing and audio in both directions.
  • Remembers the server's certificate on first connection and refuses a different certificate.
  • Chooses per vault between a balanced profile and a lossless "sharp text" profile.

Live observation

  • Allows a vault administrator to watch a running terminal session, read-only.
  • Warns the person being watched in their session, with the name of who is watching.
  • Records the observation in the journal before the first byte is read.
  • Can be turned off in the server configuration.

Import

  • Imports a KeePass database (.kdbx) with its master password, after a preview showing no secrets at all.
  • Chooses between a single vault, where groups become folders, or one vault per group.
  • Skips duplicates and the KeePass recycle bin by default, and carries over TOTP codes, custom fields and tags.
  • Imports everything or nothing, with one line in the history for each vault affected.

Vault: On your devices

  • Web: the complete application in the browser, with the SSH gateway and RDP.
  • Android: the Prophetix authenticator app, written but not yet published (one-time codes and sign-in approval).
  • Windows: the desktop client is yet to be adapted to the Prophetix sign-in and does not yet work with the current server.
  • iOS: the authenticator app's code is written, but has not been compiled.

Vault: Good to know

  • Vault is not yet offered as a subscription.
  • The gateway has only been tried with a test OpenSSH server and a test Linux desktop: not yet with a real Windows server.
  • Live observation covers terminals only, not remote desktops.
  • A recording shows everything that is displayed: it requires prior information to the people concerned and, depending on the country, consultation of their representatives.
  • Notes, custom fields and usernames are not encrypted in the database.
  • Deletion is permanent: there is no recycle bin.
  • On a phone, only its launch and the codes screen have been tried; the Google Drive backup and the link to the vault have not been tried in real conditions.

Vault: Planned (not available yet)

  • Access request with approval before a privileged session.
  • Sharing a vault with a group, certificates in the browser and export of vaults.
  • Search within recordings, SFTP, observation of a remote desktop.

Also in the subscription