Security research · detection engineering · automation · data tooling
Public-safe lab work for people who prefer logs over vibes.
ZEID DATA LAB > status
mission : evidence-first security engineering
mode : public-safe research
focus : detection logic, automation, dashboards, governance, malware analysis
rule_001 : if it cannot show receipts, it does not ship
robot_status : sarcastic, but compliant
Auto-updated from recent GitHub activity: 2026-05-16 19:31 UTC
| Repo | Latest signal | Updated |
|---|---|---|
| Research | Fix README link checker TOML config | 2026-05-16 |
Generated by .github/workflows/update-now-building.yml. If this section looks boring, the robot is either sleeping or nothing public moved.
| Area | Link | What it gives you |
|---|---|---|
| Research Lab | Research | Main public lab for security research, detections, tools, workbooks, and docs. |
| Detections | detections | KQL, Sigma, SPL, defensive analytics, and signal logic. |
| Automation | tools/scripts | Repeatable validators, collectors, and helper scripts. |
| Workbooks | workbooks | Dashboard and SOC-style visual analytics artifacts. |
| Research Notes | research | Malware research notes, experiments, and public-safe writeups. |
| Releases | release history | Versioned public drops of stable lab content. |
- Evidence first.
- Defensive and authorized.
- Public-safe by default.
- No secrets, private logs, credential material, or personal data.
- Claims need artifacts, telemetry, references, or reproducible commands.
- Automation should explain what it read, what it changed, and what proves it worked.
[active] detection engineering packs
[active] security operations playbooks
[active] public-safe malware research notes
[active] data-driven investigation tooling
[active] GitHub-native validation, releases, and documentation
Website: zeiddata.com
For sensitive security reports, use the security policy in the relevant repository.
Built for receipts, not vibes. The robot is friendly. The pipeline is not.