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!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...