Voice to Text for Security Engineers
You spend half your day writing — incident reports, vulnerability assessments, policy documents, Slack threads explaining findings to non-technical stakeholders. Blurt lets you speak all of it instead of typing. Hold a button, talk through your findings, release. Text appears wherever your cursor is — in Jira, Confluence, Splunk notes, anywhere. Your hands stay free for the real work.
The Typing Problem
Writing incident reports at 2 AM during an active breach
You're knee-deep in logs, tracking lateral movement across three systems. Leadership wants updates every 30 minutes. Every minute you spend typing the incident report is a minute you're not containing the threat. You know exactly what's happening — you could explain it in 60 seconds out loud — but typing it into the IR template takes 10 minutes you don't have.
Documenting vulnerability findings after a long assessment
You just finished a 4-hour penetration test. You found 12 issues and know exactly how to explain each one. But now you need to write detailed remediation steps for developers who won't understand the severity unless you spell it out clearly. The thought of typing 3,000 words of findings makes you want to close the laptop and deal with it tomorrow. By then, you'll have forgotten half the details.
Explaining technical security concepts to non-technical teams
Legal wants to know if the new vendor meets compliance requirements. Product wants to understand why their feature request creates a security risk. You could explain it verbally in two minutes, but the email needs to be written carefully so it's understood. You rewrite the same paragraph three times trying to simplify the technical language.
Keeping SOC runbooks and playbooks up to date
The detection rule changed last month. The escalation path is different now. Three people have asked you the same question this week because the runbook is stale. You know it needs updating, but documentation always loses to active incidents. The runbook stays outdated until the next audit panic.
Responding to security questions in multiple Slack channels
Engineering asks if they can use that new npm package. DevOps wants to know about the firewall rule change. Compliance needs confirmation on the audit evidence. Each question takes 2 minutes to type a proper response. By the time you've answered them all, an hour has vanished and your actual security work hasn't started.
How It Works
Blurt works in every tool security engineers use — Jira, Confluence, Splunk, SIEM dashboards, Slack, email. Anywhere you can put a cursor.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening.
Talk naturally
Describe the vulnerability, explain the incident timeline, or draft your policy section.
Release and done
Text appears at your cursor. No copying, no pasting, no extra steps.
Real Scenarios
Documenting incidents in real-time during response
Active incident. You just identified the entry point and need to update the IR channel. Hold your hotkey and say 'Initial access via phishing email received by finance team at 14:32 UTC. Payload executed persistence mechanism in registry run keys. Currently isolating affected endpoints and collecting memory dumps.' Posted in 8 seconds instead of 2 minutes of typing while the threat actor is still active.
Writing vulnerability remediation guidance
You found an IDOR vulnerability in the API. Developers need specific fix instructions. Hold button and speak: 'The get user endpoint doesn't validate that the requesting user owns the resource. Add authorization check to verify requesting user ID matches the resource owner before returning data. See OWASP access control cheat sheet for implementation pattern.' Clear guidance written in 15 seconds, not 3 minutes.
Explaining security decisions to leadership
The CISO wants to know why you're recommending against the vendor. Hold and talk through it: 'Their SOC 2 report shows three exceptions in access management. They don't support SSO, which means we can't enforce our MFA policy. The data residency terms conflict with our GDPR obligations.' Executive summary drafted while the context is fresh.
Updating runbooks and playbooks
The phishing response playbook needs the new escalation path. Instead of putting it off, hold the button and say 'Step 4 updated: If more than 5 users clicked the link, escalate immediately to IR lead and notify legal within 30 minutes per the updated breach notification policy.' Runbook stays current because updating it takes 10 seconds.
Responding to security review requests in Slack
A developer asks if they can add a new dependency to the codebase. Hold and respond: 'Checked the package. Last updated 8 months ago, no known CVEs, but only 200 GitHub stars and one maintainer. I'd recommend finding an alternative with more active maintenance or vendoring the specific functions you need.' Thoughtful response in 12 seconds instead of typing for 2 minutes.
Writing policy documentation sections
The access control policy needs a section on privileged account management. Talk through what you know: 'All privileged accounts must use hardware MFA tokens. Shared admin accounts are prohibited. Privileged access must be requested through the PAM system with manager approval and expires after 8 hours unless renewed.' First draft done in 20 seconds. Edit from there.
Adding notes to Jira security tickets
You just finished investigating a potential alert. The ticket needs your findings. Hold and speak: 'False positive. The traffic pattern matched our detection rule but originated from the authorized vulnerability scanner running its weekly scan. Updated the rule to exclude scanner source IPs.' Ticket documented immediately, not three days later when you can't remember what happened.
Why security engineers choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone icon or 'Hey Siri' |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical vocabulary | Handles security terms accurately | Struggles with CVE, SIEM, IDOR, etc. |
| Reliability | Consistent accuracy across sessions | Often fails silently or mishears |
| Privacy | No persistent audio storage | Apple may retain voice data |
| Workflow fit | Designed for rapid documentation | Built for casual consumer use |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt