We use cookies
We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy
Security event monitoring
A security event history for your cloud and servers
See what happened and when. SeqOps keeps a history of security events from your cloud accounts and servers. Your plan sets the window: 14, 30 or 45 days. Export it when you need a record.
- 14-day free trial
- Read-only cloud access
- First results within 24 hours
The questions come after the fact
When something looks wrong, the first questions are simple. What happened? On which server? When did it start? Without a history, your team pieces the answer together from memory and scattered screenshots.
SeqOps keeps a history of security events next to your findings and alerts. Go back through recent events, open a server’s own event history and export what you need.
It’s a working history for investigations, not a SIEM or a long-term log archive. Keep those tools for long-term storage and correlation.
What the event history covers
- A Recent Events feed on the dashboard, across your connected cloud accounts and servers
- Device Events: the event history for each server
- Log Explorer on each server, next to its events
- Events shown alongside each server’s vulnerabilities, configuration and compliance results
- Retention by plan: 14 days on Core, 30 on Edge, 45 on Max, custom on Enterprise
- Storage by plan: 3 GB on Core, 5 GB on Edge, 7 GB on Max
- Export to CSV, PDF or Excel for each server’s data and for alert data
- Signed webhooks to send alerts to your SIEM or other tools
How the history builds up
Step 1: Connect cloud and servers
Connect cloud accounts with read-only access and install the agent on your Windows and Linux servers. Data starts to appear within 24 hours of connecting (6–24 hours).
Step 2: Review recent events
Check the Recent Events feed on the dashboard. Open a server to see its event history in the Device Events tab, next to its findings.
Step 3: Export what you need to keep
Your plan keeps 14, 30 or 45 days of history. For anything longer, export to CSV, PDF or Excel, or send alerts on through signed webhooks.
What you get
Context next to every server
See a server’s events, findings and configuration on one page. When an alert comes in, the first questions are quicker to answer.
A clear retention window
History is kept for 14, 30 or 45 days, depending on your plan. You always know how far back you can look.
Records you can hand over
Export a server’s data or your alert data to CSV, PDF or Excel. Share it with management, auditors or the people handling an incident.
A fit with your existing tools
Keep your SIEM for long-term storage and correlation. Signed webhooks send alerts on to it, so both tools see the same issues.
Where your history is kept
Event data comes from read-only cloud connections and the server agent, which uses outbound HTTPS only. It’s stored in AWS eu-north-1 (Stockholm), with TLS in transit.
Retention follows your plan while your account is active. Deleting a server can permanently remove its history, so export what you need first.
Visit the Trust CenterFrequently asked questions
Is SeqOps a SIEM?
How long is event history kept?
Can I export events?
Can I use the history for an investigation?
Where does event data come from?
Read the guides
Related on the platform
- Security alerts
Alerts ranked by severity, with AI-powered fix guidance, sent where your team works.
- Server scanning
Find vulnerabilities on Windows and Linux servers with a lightweight agent.
See what’s exposed in your cloud and servers
Start your 14-day free trial and get your first results within 24 hours.