Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Splunk Exam SPLK-1003 Topic 14 Question 111 Discussion

Actual exam question for Splunk's SPLK-1003 exam
Question #: 111
Topic #: 14
[All SPLK-1003 Questions]

What is the correct example to redact a plain-text password from raw events?

Show Suggested Answer Hide Answer
Suggested Answer: B

The correct answer is B. in props.conf:

[identity]

SEDCMD-redact_pw = s/password=([^,|/s]+)/ ####REACTED####/g

According to the Splunk documentation1, to redact sensitive data from raw events, you need to use the SEDCMD attribute in the props.conf file. The SEDCMD attribute applies a sed expression to the raw data before indexing. The sed expression can use the s command to replace a pattern with a substitution string. For example, the following sed expression replaces any occurrence of password= followed by any characters until a comma, whitespace, or slash with ####REACTED####:

s/password=([^,|/s]+)/ ####REACTED####/g

The g flag at the end means that the replacement is applied globally, not just to the first match.

Option A is incorrect because it uses the REGEX attribute instead of the SEDCMD attribute. The REGEX attribute is used to extract fields from events, not to modify them.

Option C is incorrect because it uses the transforms.conf file instead of the props.conf file. The transforms.conf file is used to define transformations that can be applied to fields or events, such as lookups, evaluations, or replacements. However, these transformations are applied after indexing, not before.

Option D is incorrect because it uses both the wrong attribute and the wrong file. There is no REGEX-redact_pw attribute in the transforms.conf file.

References: 1: Redact data from events - Splunk Documentation


Contribute your Thoughts:

Annamaria
21 days ago
Haha, this question is a real mind-bender. I'm just going to pick Option A and hope for the best. Password redaction can't be that complicated, right?
upvoted 0 times
...
Romana
22 days ago
Hmm, this is a tricky one. I'm going to go with Option D just because it sounds more secure to use REGEX in the transforms.conf file.
upvoted 0 times
...
Martin
23 days ago
I disagree, I think Option C is the right answer. Using transforms.conf with SEDCMD is the standard way to redact sensitive information like passwords.
upvoted 0 times
Ellsworth
5 days ago
I think Option A is the best choice. Using props.conf with REGEX-redact_pw is a more efficient way to redact plain-text passwords.
upvoted 0 times
...
Jame
18 days ago
Option C is the correct answer. Using transforms.conf with SEDCMD is the standard way to redact sensitive information like passwords.
upvoted 0 times
...
...
Stephane
26 days ago
I see your point, maybe C) is better for redacting passwords in raw events.
upvoted 0 times
...
Carey
1 months ago
But A) uses REGEX while C) uses SEDCMD, which one do you think is more appropriate?
upvoted 0 times
...
Stephane
1 months ago
I disagree, I believe it is C) in transforms.conf.
upvoted 0 times
...
Vashti
1 months ago
Option B looks like the correct way to redact a password in the props.conf file. Using SEDCMD instead of REGEX seems more appropriate for this task.
upvoted 0 times
Evangelina
10 days ago
User3: I agree, using SEDCMD for redacting passwords is more suitable.
upvoted 0 times
...
Reed
13 days ago
User2: Yeah, SEDCMD in props.conf seems like the right choice.
upvoted 0 times
...
Stefania
21 days ago
User1: I think option B is the way to go.
upvoted 0 times
...
...
Carey
1 months ago
I think the correct example is A) in props.conf.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77