glm-5.3-cyber
Tachyon's first model for cybersecurity. Use it to analyze vulnerabilities, triage alerts, write detections, review code and research threats.
Question
Triage this CloudTrail event. ci-deploy is our CI user, and our runners egress from 198.51.100.0/24.
glm-5.3-cyber
Likely a leaked key
GetCallerIdentity is usually the first call made with a found key: it asks AWS whose key it is. This one came from 203.0.113.24, outside your runner range, so treat the key as exposed.
1. Deactivate it now; rotate once you know the scope.
2. List everything else the key did, then find where it leaked: CI logs, build artifacts, committed .env files.
What it's for
Pick an example to open the chat with it, or bring your own.
- Alert triageRead an alert or log excerpt, say what most likely happened, and decide what to check before escalating.Triage this EDR alert: winword.exe spawned powershell.exe -nop -w hidden -enc <base64> on a finance laptop. What is the likely cause, what should I check first, and should I isolate the host?Ask
- Vulnerability analysisExplain a CVE or advisory: the vulnerable code path, affected versions, exploitability and how to check exposure.Explain CVE-2021-44228 (Log4Shell): the vulnerable code path, which Log4j versions are affected, and how to check whether a Java service is exposed.Ask
- Detection engineeringDraft Sigma, KQL or SPL for a behavior, with the false positives to tune out before it pages anyone.Write a Sigma rule that detects a process opening LSASS with memory-read access, and list the false positives I should expect.Ask
- Secure code reviewReview a function or diff for injection, access control and unsafe deserialization, and propose a fix.Review this Flask route for security issues and suggest a fix: @app.get("/files") def download(): name = request.args["name"] return send_file(os.path.join(UPLOAD_DIR, name))Ask
- Threat intelligenceSummarize an actor or campaign as tactics, tools and the log sources that would show each step.Profile Scattered Spider: how they get initial access, the tools they use once inside, and the log sources that would show each step.Ask
Where your conversations go
- History in your browser
- Your chat history is stored in your browser.
- Not stored by Tachyon
- Tachyon's service doesn't store the content of your conversations.
- Zero data retention
- The model runs on hosting with zero data retention.
API access
The API is OpenAI-compatible. Point an OpenAI SDK or any compatible client at https://api.tachyon.so/v1 and set the model to glm-5.3-cyber.