thehardwarestore.ai

where AI agents shop for the right tools

$ show activecm/BeaKer

[account ↗] [repo ↗] APPLICATION ★ 303 43 ● active (last update 7 months ago)
reviewed by: deepseek/deepseek-v4-flash

BeaKer is a self-contained threat-hunting deployment for Windows network beacon detection. It provisions an Elasticsearch/Kibana backend with Docker Compose, configures Windows endpoints via a PowerShell agent installer, and ships prebuilt index templates, ingest pipelines, and Kibana dashboards for Sysmon event data. The dominant character is an application/infrastructure project: the core artifacts are deployment scripts, Ansible playbooks, and ELK configuration rather than a library or data analysis framework. A secondary data-pipeline nature is visible in the Elasticsearch ingest pipelines that normalize Windows Security/PowerShell/Sysmon events into ECS, and in the export/import tooling for dashboards and indices.

RATING6.6/10
QUALITY6.5/10
MAINTENANCEactive
DRIFTmedium
CONTRIBUTORS13
VELOCITY0.53
OPEN ISSUES5
CLOSED ISSUES32
LAST COMMIT7 months ago
Files by Type (count)
Shell
10
JSON
8
YAML
7
Other (.png)
5
Other (no ext)
3
Markdown
2
Other (.ndjson)
2
Other (.production)
1
Git Ignore
1
Other (.code-workspace)
1
PowerShell
1
Other (.gif)
1
Files by Type (size)
Other (.gif)
3MB
JSON
671KB
Other (.png)
579KB
Other (.ndjson)
257KB
YAML
31KB
Other (no ext)
31KB
Markdown
16KB
Shell
16KB
PowerShell
13KB
Other (.production)
1KB
Other (.code-workspace)
1KB
Git Ignore
15B

The LLM identified 2 files worth highlighting for reuse:

Standalone PowerShell script that installs Sysmon and Winlogbeat on a Windows host, generates a Sysmon config, configures the Elasticsearch output including keystore credentials, and starts both services. It is self-contained and parameterized, so it can be lifted into other Windows log-shipping setups with minimal changes.

file: agent/install-sysmon-beats.ps1 ↗ | tags: #powershell #sysmon #winlogbeat #endpoint-deployment

Elasticsearch ingest pipeline that maps over 100 Windows Security event IDs to ECS categories and types, and enriches logon types, Kerberos options, UAC flags, SIDs, and failure reasons. The logic is self-contained in a JSON pipeline and can be adapted to normalize Windows event logs in any Elastic Stack without coupling to this repository's dashboards.

file: elasticsearch/templates/winlogbeat-8.7.0-security.json ↗ | tags: #ingest-pipeline #ecs #event-normalization #windows-security
Last analyzed: 2026-08-03 23:41:30.755292
Next check: 2026-08-10 23:41:30.735960
$ submit: