Security

Splunk Attack Range 3.0

Sharath22
New Member

Hello Team, as we delve into Splunk Attack Range 3.0, we're interested in understanding the MITRE ATT&CK tactics and techniques that can be simulated within this environment. If you have information on this, kindly share it with us. Thank you!

0 Karma

inventsekar
SplunkTrust
SplunkTrust

Hi @Sharath22 maybe, pls update how much you have configured the attack range, which things you have installed, did you try to simulate any attacks, etc.. thanks. 

0 Karma

bchip
New Member

Failing to Build Attack Range 3.0 on Linux Mint 21.2  (ubuntu codename jammy)

I have been following installation instructions on https://attack-range.readthedocs.io/en/latest/Attack_Range_Local.html  for a attack range local install on linux

Attack range fails during the build process  (python attack_range build)

<--output cut-->

ASK [phantom : Creates directory] *********************************************
changed: [ar-phantom-attack-range-key-pair-ar]

TASK [phantom : Copy Splunk SOAR to server] ************************************
[WARNING]: Error deleting remote temporary files (rc: 1, stderr: Could not
chdir to home directory /home/vagrant: Permission denied bash:
/home/vagrant/.bashrc: Permission denied })
changed: [ar-phantom-attack-range-key-pair-ar]

TASK [phantom : prepare phantom install script without apps] *******************
fatal: [ar-phantom-attack-range-key-pair-ar]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /home/vagrant/.ansible/tmp `\"&& mkdir \"` echo /home/vagrant/.ansible/tmp/ansible-tmp-1716446324.3823583-133581-59531706665728 `\" && echo ansible-tmp-1716446324.3823583-133581-59531706665728=\"` echo /home/vagrant/.ansible/tmp/ansible-tmp-1716446324.3823583-133581-59531706665728 `\" ), exited with result 1", "unreachable": true}

PLAY RECAP *********************************************************************
ar-phantom-attack-range-key-pair-ar : ok=2 changed=2 unreachable=1 failed=0 skipped=6 rescued=0 ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
2024-05-23 08:38:44,768 - ERROR - attack_range - vagrant failed to build

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

    Thursday, June 25, 2026  |  11AM PDT / 2PM EDT  Duration: 1 Hour (Includes live Q&A) Register to ...

Analytics Workspace deprecation

As of Splunk Cloud Platform 10.4.2604 and Splunk Enterprise 10.4, Analytics Workspace is now deprecated. ...

Splunk Developer Day Recap: Building, Publishing, and Growing on the Splunk Platform

Splunk Developer Day brought the Splunk developer community together for a practical look at what it means to ...