deixic
Log inRequest a demo

SurfacesAvailable

Hand Dex a failing control from Teams.

Dex, listening for a message

Mention Dex in a channel or message it directly with a failing control or a security finding. Teams carries the request and the progress notices. A change that needs a named approver is decided in the Deixic app queue or in Slack.

Request early access

A request and its notices in the thread.

Example thread with demo data. Control CC7.2 is failing.

  1. Dana Ortiz

    @Dex CC7.2 is failing: no alert when the root account signs in. Fix it.

  2. Dex

    Ran within policy: created the sign-in alert rule, read it back, and it matches. The test re-run is passing.

  3. Dex

    A second finding needs a named approver. The decision link opens the app queue. I will post the result here.

  4. Dex

    Approved in the app by Priya Shah. CC6.3 is closed. The receipt is in the app.

  • Requests from the people who see the alert

    Anyone in your organization can mention Dex with the failing control or finding. Each person links their account, so Dex acts with their access and nothing more.

  • Notices in the thread

    Progress, closures, and decisions that are waiting come back to the channel thread, where everyone who asked can see them.

  • Approvals stay in the app or Slack

    The decision link in a Teams notice goes to the app. The result comes back to the Teams thread.

  • Pick it up anywhere

    The same thread continues in the app, where the receipts live.

Example Teams exchange about a missing AWS root sign-in alert, its readback, and a separate approval still open.
Example exchange with demo data: fix within policy and keep the remaining decision visible.

All surfaces.