Security

Splunk Attack Range

SecBit
Observer

A question regarding the splunk attack range

I am using the attack_range and not the attack_range_local repository as it says the local repository has been archived, should I be using the attack_range_local even though it says the attack_range now support a local install.

I have specified the provider as local in the configuration but I keep getting errors related to azure or aws

I can configure the attack range no problem and I select the local option but I get errors when trying to build the attack range.

Any help is much appreciated!!!

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!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...