Skip to content

elastic/security-documents-generator

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

34 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Generating fake alerts

Getting started

copy config.dev.json to config.json

  1. Install dependecies yarn

  2. Change config.json and provide credentials for elasticsearch.

You can proide apiKey for Cloud/Serverless, or just username/password

Examles of config:

{
    "elastic": {
        "node": "https://test.es.us-west2.gcp.elastic-cloud.com",
        "apiKey": "ASdlkk=="

    },
    "kibana": {
        "node": "https://test.kb.us-west2.gcp.elastic-cloud.com:9243",
        "apiKey": "asdasdasd=="
    }
}
{
    "elastic": {
        "node": "http://localhost:9200",
        "username": "elastic",
        "password": "changeme"
    },
    "kibana": {
        "node": "http://127.0.0.1:5601",
        "username": "elastic",
        "password": "changeme"
    },
    "eventIndex": ""
}

Commands

Entity store

yarn start entity-store - Generate data for entity store

yarn start clean-entity-store - Clean data for entity store

Alerts

yarn start help - To see the commands list

yarn start generate-alerts <n> - Generate n alerts

yarn start delete-alerts - Delete all alerts

Api tests

yarn start test-risk-score - Test risk score API time response

Alert document

To modify alert document, you can change createAlert.ts file.

How to test Risk Score Api

Example list of command for testing Risk Score API woth 10.000 alerts.

yarn start delete-alerts
yarn start generate-alerts 10000
yarn start test-risk-score

How to generate data for serverless project

  1. Get your Elasticsearch url.

    Go to Cloud -> Projects -> Your serverless project.

    Then click Endpoints -> View and copy paste your ES URL to config.json into elastic.node field.

  2. Generate API key

    Go to Cloud -> Projects -> Api Keys -> Manage project API keys

    Create a new API key and past it to config.json into elastic.apiKey field.

  3. (Optional) Change if you want index name in config.json in eventIndex field.

    By default - logs-testlogs-default

  4. (Optional) Change mappings in eventMappings.json file.

  5. (Optional) Change event structure in createEvents.ts file

  6. Run yarn start generate-events n. Where n is the amount of documents that will be generated.

  7. yarn start delete-events to remove all documents from event index after your test.

About

Generate fake security data for testing

Resources

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •