Cyber security

RedELK – Essential Naming Requirements For Deployment

In the complex landscape of RedELK deployment, adhering to precise naming requirements is crucial for operational success.

This article delves into the essential naming conventions necessary for a smoothly functioning RedELK setup.

From FilebeatID to Redirector configurations, understand the specifics that ensure your cybersecurity infrastructure is effective and efficient.

For a properly working RedELK setup it is required to pay attention to the following requirements.

NameDescriptionSpecifics to pay attention to
FilebeatIDName given to the host by Filebeat.
The name is given during running the install-redir.sh or install-c2server.sh scripts.

For the c2 servers: have the identifier match the name in the mounts/redelk-config/etc/cron.d/redelk and the name passed to install-c2server.sh script

If entered incorrectly during installation, background scripts will fail and implant log files, screenshots and keystrokes will not be accessible via RedELK interface. You can change it in the /etc/filebeat/filebeat.yml config file on the specific host or in mounts/redelk-config/etc/cron.d/redelk on the RedELK server
attackscenarioName of the attack scenario this infra component belongs to.An infra component can only belong to a single attackscenario.

In case of TIBER or the likes this will likely be something like scenario1, scenario2 and scenarioX. Could also be more descriptive, e.g. ransomware, fingain, or your internally used code name.

Name needs to be the same for all other components in the same scenario; it is an important way for filtering within the Kibana interface.

The name is given during running the install-redir.sh or install-c2server.sh scripts. If entered incorrectly during installation, you can change it in the /etc/filebeat/filebeat.yml config file on the specific host.
Redirector backendName given in the config of the redirector application (Apache, HAProxxy, etc) for the backend.Must start with c2 or decoy

Use a descriptive name, e.g. decoy-phishrun1 or c2-https.

Stock Kibana views and dashboards expect the naming standard. Some alarms are hardcoded triggered for these c2* names
Redirector frontendName given in the config of the redirector application (Apache, HAProxxy, etc) for the frontend.Let it be descriptive for you as you will use this in the RedELK interface to understand where traffic was coming in. Better not use spaces in the name.
Varshini

Varshini is a Cyber Security expert in Threat Analysis, Vulnerability Assessment, and Research. Passionate about staying ahead of emerging Threats and Technologies.

Recent Posts

groupdel Command in Linux: Remove a Group and Audit Files

The groupdel command in Linux removes a group from the system. It deletes the group's entry from /etc/group and /etc/gshadow,…

16 hours ago

wc Command in Linux: Count Lines, Words, Characters, and Bytes

The wc command in Linux counts lines, words, characters, and bytes in files or standard input. It…

16 hours ago

top Command in Linux: Monitor Processes and Resource Usage

The top command in Linux provides a real-time view of running processes and system resource usage. From…

16 hours ago

usermod Command in Linux: Modify User Accounts and Groups

The usermod command in Linux modifies existing user account attributes. You can use it to manage group…

17 hours ago

sort Command in Linux: Sort Text, Numbers, Columns, and More

The sort command in Linux reads lines from files or standard input and writes them to standard…

2 days ago

wall Command in Linux: Broadcast Messages to Logged-In Users

The wall command in Linux sends a message to the terminals of all currently logged-in users. The…

2 days ago