Generated banner for Security Generate Security Sample Data
Generated logo for Security Generate Security Sample Data

Security Generate Security Sample Data

ElasticOfficialCreated by elastic

  • Skill
  • Tool integration
  • Security
  • Apache-2.0
  • Medium risk
  • Has scripts

From the author

Generate sample security events, attack scenarios, and synthetic alerts for Elastic Security. Use when demoing, populating dashboards, testing detection rules, or setting up a POC.
— the description by elastic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This tool provides a command-line interface to inject synthetic, ECS-compliant security data into Elastic Security. It supports generating raw events from common sources like Windows, AWS, and Okta, as well as complex, multi-step attack scenarios and pre-indexed synthetic alerts. Designed for demo environments, POCs, and detection rule validation, it allows users to populate dashboards and test security features without requiring live traffic. The tool includes a continuous mode for simulating active environments and a cleanup utility to remove all injected data.

What it does

  • Generates synthetic security events for system, endpoint, Windows, AWS, and Okta data streams.
  • Simulates multi-step attack scenarios such as ransomware chains and credential theft.
  • Creates synthetic alert documents with MITRE ATT&CK mappings and risk scores.
  • Supports continuous event streaming to simulate active SOC environments.
  • Provides a cleanup utility to safely remove all generated sample data.
  • Integrates with Elastic Security dashboards, Alerts tab, and Attack Discovery.

When to use it

  • When you need to populate Elastic Security dashboards for a product demonstration.
  • When testing the efficacy of detection rules against specific attack patterns.
  • When setting up a Proof of Concept (POC) environment with realistic security data.
  • When you need to verify the configuration of Attack Discovery or other security features.

Advantages

  • Enables rapid environment setup without needing real-world security logs.
  • Uses safe, non-malicious data that mimics real attack chains.
  • Provides granular control over data generation via CLI flags.
  • Includes built-in cleanup functionality to maintain environment hygiene.
  • Supports continuous simulation for realistic dashboard activity.

Usage examples

“Set up a demo environment so I can show Attack Discovery to my VP.”
Executes the demo-walkthrough script to generate a full suite of sample data and opens the Kibana interface.
“Generate only the ransomware attack chain to test our detection rules.”
Runs the sample-data script with the ransomwareChain scenario flag to inject relevant events and alerts.
“Keep generating events so the dashboards stay active during the demo.”
Starts the continuous generation mode, streaming events at the specified interval until manually stopped.
“Remove all sample data from my project.”
Executes the cleanup command to delete all documents tagged as sample data from the Elasticsearch indices.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/elastic/security-generate-security-sample-data/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip security-generate-security-sample-data.zip -d .agents/skills

Documentation by elastic

Generate Security Sample Data

Generate ECS-compliant security events, multi-step attack scenarios, and synthetic alert documents that populate Elastic Security dashboards, the Alerts tab, and Attack Discovery.

Quick start

For a zero-friction experience that generates everything and opens Kibana:

node skills/security/generate-security-sample-data/scripts/demo-walkthrough.js

Workflow

- [ ] Step 1: Set environment variables
- [ ] Step 2: Generate sample data
- [ ] Step 3: Explore in Kibana
- [ ] Step 4: Clean up when done
Step 1: Set environment variables
export ELASTICSEARCH_URL="https://your-project.es.region.aws.elastic.cloud"
export ELASTICSEARCH_USERNAME="admin"
export ELASTICSEARCH_PASSWORD="your-password"
export KIBANA_URL="https://your-project.kb.region.aws.elastic.cloud"
Step 2: Generate sample data
Generate everything at once
node skills/security/generate-security-sample-data/scripts/sample-data.js \
  system endpoint okta aws windows --scenarios --alerts
Generate only events
node skills/security/generate-security-sample-data/scripts/sample-data.js \
  system endpoint --count 100
Generate only attack scenarios
node skills/security/generate-security-sample-data/scripts/sample-data.js --scenarios
Generate only synthetic alerts
node skills/security/generate-security-sample-data/scripts/sample-data.js --alerts
Step 3: Explore in Kibana

After generating data, direct the user to these pages:

  • Security > Alerts — synthetic alerts with MITRE ATT&CK mappings

  • Security > Attack Discovery — requires an LLM connector to analyze alerts

  • Security > Hosts — host activity from sample events

  • Security > Overview — summary of all security data

  • Discover — raw events across all data streams

Step 4: Clean up when done
node skills/security/generate-security-sample-data/scripts/sample-data.js --cleanup

What gets generated

Sample data spans 5 packages (system, endpoint, windows, aws, okta) and 4 focused attack scenarios covering the most common demo themes: Windows credential theft, AWS cloud privilege escalation, Okta identity takeover, and a full ransomware kill chain. Synthetic alert documents are indexed into .alerts-security.alerts-default with MITRE ATT&CK mappings, severity levels, and risk scores.

All events use RFC 5737 / RFC 2606 safe addresses. For full tables of packages, scenarios, and alerts see references/sample-data-reference.md.

Continuous mode

Stream events to simulate a live environment:

node skills/security/generate-security-sample-data/scripts/sample-data.js \
  --continuous --interval 15

Every 5th batch includes an attack scenario; every 10th batch adds synthetic alerts. Press Ctrl+C to stop.

Tool reference

sample-data.js
FlagDescription
--count, -nEvents per package (default: 50)
--scenariosRun all attack simulation scenarios
--scenario NAMERun a specific scenario
--alertsGenerate synthetic alert documents
--cleanupRemove all sample data and alerts
--continuousStream live events (Ctrl+C to stop)
--interval NSeconds between continuous batches (default: 30)
--json, -jOutput results as JSON
--yes, -ySkip confirmation prompts
demo-walkthrough.js

Zero-friction runner that generates everything and opens Kibana.

FlagDescription
--cleanupRemove all sample data, alerts, case
--continuousGenerate then stream live events
--count NEvents per package (default: 50)
--interval NSeconds between batches (default: 30)

Examples

Quick demo for a stakeholder

"Set up a demo environment so I can show Attack Discovery to my VP."

node skills/security/generate-security-sample-data/scripts/demo-walkthrough.js
Targeted scenario testing

"Generate only the ransomware attack chain to test our detection rules."

node skills/security/generate-security-sample-data/scripts/sample-data.js \
  --scenario ransomwareChain --alerts
Simulating a live SOC

"Keep generating events so the dashboards stay active during the demo."

node skills/security/generate-security-sample-data/scripts/demo-walkthrough.js --continuous
Cleaning up after a demo

"Remove all sample data from my project."

node skills/security/generate-security-sample-data/scripts/sample-data.js --cleanup

Guidelines

  • All generated documents are tagged with tags: ["elastic-security-sample-data"] for safe cleanup. The cleanup command only deletes documents with this marker.

  • If marker fields are not indexed in a data stream, cleanup falls back to scanning _source.tags for matching sample documents from the last 14 days.

  • Synthetic alerts are indexed directly into .alerts-security.alerts-default — they do not require detection rules to be installed or enabled.

  • Attack Discovery requires an LLM connector (OpenAI, Anthropic, Google Gemini, or similar) configured in Kibana under Stack Management > Connectors. The "Complete" project tier unlocks the feature, but the connector must be set up separately.

  • Use the case-management skill for creating investigation cases from alerts.

Production use

  • Do not run against production clusters unless you intend to inject synthetic data alongside real alerts. Sample events and alerts are tagged for cleanup but will appear in dashboards, the Alerts tab, and Attack Discovery alongside real data.

  • All write operations (generate, --cleanup, --continuous) prompt for confirmation. Pass --yes or -y to skip when called by an agent.

  • --cleanup runs deleteByQuery across all sample data indices — verify environment variables point to the intended cluster before running.

  • --continuous mode indexes events indefinitely until manually stopped with Ctrl+C.

Environment variables

VariableRequiredDescription
ELASTICSEARCH_URLYesElasticsearch URL
ELASTICSEARCH_API_KEYYes*Elasticsearch API key
ELASTICSEARCH_USERNAMEYes*Elasticsearch username (alternative)
ELASTICSEARCH_PASSWORDYes*Elasticsearch password (alternative)
KIBANA_URLNoKibana URL (for case creation and links)
KIBANA_USERNAMENoKibana username (if using Kibana features)
KIBANA_PASSWORDNoKibana password (if using Kibana features)

*Either API key or username/password is required for Elasticsearch.

Files

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Elasticsearch BV

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key, Needs Node.js

The author says: Requires Node.js 22+, network access to Kibana and Elasticsearch. Environment variables: KIBANA_URL plus KIBANA_API_KEY or KIBANA_USERNAME/KIBANA_PASSWORD; ELASTICSEARCH_URL or ELASTICSEARCH_CLOUD_ID plus ELASTICSEARCH_API_KEY or ELASTICSEARCH_USERNAME/ELASTICSEARCH_PASSWORD.

Security

What our scanner noticed· Medium risk

  • Encoded commands that are executed
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
elastic
Publisher
Elastic (Official)
Source
elastic/agent-skills · skills/security/generate-security-sample-data · commit 09d879d
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
elastic/agent-skills

AutoGineer is not affiliated with or endorsed by elastic or Elastic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download security-generate-security-sample-data.zip