# Phishing reports, prod access and Okta alerts, handled in Slack and Teams

Risotto gives your security team its own help desk in Slack and Microsoft Teams. Someone clicked a link in a fake DocuSign email? Risotto finds out whether they typed their password, resets it, ends their sessions and checks the Okta log, then brings in Security with the facts. An engineer needs production access during an outage, and gets two hours, approved by Security and removed on time. A question about the AI policy gets an answer from the policy itself.

[Book a demo](/demo) · [Security and trust](/security)

## Phishing reports, contained before Security opens the ticket

Risotto works a phishing report the way your runbook says. It asks whether the person only opened the email, clicked or typed their password. If they typed it, Risotto resets the password, ends their sessions and checks the Okta log for new sign-ins, then hands Security a ticket that already says what happened. A stolen laptop gets the same treatment: locked in Jamf or Iru, sessions ended, Security told.

[Start from the runbook](/library/runbooks/suspected-phishing-report)

## When Okta flags an account, Risotto checks it first

Risotto acts when Okta reports a change, not only when someone asks. When Okta suspends an account, a Risotto automation reads that person's Okta log for the day before, signs them out of Google Workspace, posts what it found in your alerts channel and opens a ticket for Security. A locked account gets a message to its owner and a ticket, and nobody unlocks it until IT confirms who they are. Posts from your alerting tools in a Slack channel become tickets too.

[Automations](/product/automations)

## Production access, measured in hours

With Risotto, an engineer asks for production access in Slack or Teams, says why, and Security approves it. The access lands in Okta, Microsoft Entra ID, Google Workspace or JumpCloud and is removed when its time is up, even if that's two hours from now. Renewals can require a fresh approval, and self-approval can be blocked.

**91%** autosolve rate on access requests at Ironclad. [Read the story](/customers/ironclad-transforms-90-percent-it-support-with-risotto)

> "For sensitive tools and resources Risotto's automated time-based access has been a game-changer." — Collin Clifford, Legal & Compliance Manager, Superhuman

[Identity governance](/use-cases/iga-automation) · [Access requests](/product/access-requests)

An access rule's time limits: how long access can last, and whether a renewal needs a new approval. Example data.

## Security's queue stays Security's

Security joins Risotto as its own department. Only Security's Agents and Supervisors see its tickets: an admin role elsewhere in Risotto doesn't add them, and every change to who's in the department is recorded in the audit log. Security keeps its own runbooks and its own credentials in Risotto's credential vault, which only Security's tools can use.

[See every team](/solutions)

## Evidence your auditor can read

Every request in Risotto keeps its record on the ticket: who asked, who approved, what ran and when. The audit log records every configuration change with the old and new values, and the audit-events API streams those changes to your SIEM. The access grants page shows who has what until when, and exports to CSV.

> "We always wanted to require a reason for application access, but it was really difficult to integrate that into JSM. Risotto adds that functionality to JSM and so much more." — Tom Grinberg, IT Manager, Trust & Will

[Security and trust](/security)

Risotto's audit log: each configuration change with who made it, when, and the values before and after. Example data.

## The AI works inside your limits

Risotto acts only inside the limits you set, and each one is something you can check.

- **Approvals before changes.** Write a rule once, such as "contractors need IT approval", and it applies to access rules, tools and runbook steps.
- **Proof of who's asking.** An Okta Verify push or a sign-in to your company's Okta comes before sensitive changes.
- **The AI can't loosen a rule.** The Assistant can add an approval requirement to a tool, but only a person can remove one.
- **Secrets the AI never sees.** Credentials are write-only and sent only to the hosts you approve.
- **Files scanned.** Attachments are scanned for malware.
- **SOC 2 Type II.** HIPAA on the Enterprise plan (we sign BAAs), and zero data retention with model providers.

[Security and trust](/security)

## Start from the library

Start from one of these and change it to fit. Open one to see every step and tool, or [browse the library](/library).

### When something looks wrong

Contain first, then bring in Security.

- [Suspected phishing report](/library/runbooks/suspected-phishing-report): reset and sign out only if they typed their password, then bring in security
- [Lost or stolen laptop](/library/runbooks/lost-or-stolen-laptop): lock the Mac in Jamf, end every session and alert security
- [Suspended Okta account review](/library/automations/okta-suspended-account-review): read the day's Okta log, sign out of Google Workspace and alert security
- [Locked Okta account follow-up](/library/automations/okta-locked-account-follow-up): tell the person, open a ticket, and unlock only after IT confirms who they are

### Proof of who's asking

Checks before a reset or a recovery key.

- [Okta account recovery with risk checks](/library/runbooks/okta-account-recovery-with-risk-checks): check the log for repeat resets and new countries, then unlock, reset or clear MFA
- [Iru FileVault recovery with identity check](/library/runbooks/iru-filevault-recovery-documented): a push to the person's phone before the key goes out

### Who gets in

Every grant follows your rules.

- [Okta group access request](/library/runbooks/okta-group-access-request): check your access rules, get the approval, add the person to the group
- [Slack Connect invite review](/library/automations/slack-connect-invite-review): approve partners and deny the rest, with an admin's OK

## Frequently asked questions

### Can Risotto handle phishing reports in Slack?

Yes. Risotto asks the person what happened, and if they typed their password, it resets it, ends their sessions and checks the Okta log before it brings in Security. The steps come from a runbook you can read and change. [Suspected phishing report](/library/runbooks/suspected-phishing-report)

### Can Risotto give engineers time-bound production access?

Yes. Risotto grants access through your identity provider after the approval your policy names, and removes it when the time your rule sets is up, even if that's two hours. [Access requests](/product/access-requests)

### Can Risotto act on Okta events such as a suspended account?

Yes. A Risotto automation can start when Okta reports an account created, activated, suspended, deactivated or locked out, and run the checks you describe, such as reading the Okta log and opening a ticket for Security. [Automations](/product/automations)

### Can the security team keep its own private queue in Risotto?

Yes. Security gets its own department in Risotto. Only its Agents and Supervisors see its tickets, and an admin role elsewhere in Risotto doesn't add them. [See every team](/solutions)

### Can Risotto's AI change our systems on its own?

Only inside the limits your team sets. Risotto collects the approvals your policy requires before each change, and only a person can remove a tool's approval requirement. [Security and trust](/security)

## Hand Risotto the next phishing report

[Book a demo](/demo)

Source: https://www.tryrisotto.com/solutions/security
