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

Palo Alto Networks Exam PCCSE Topic 5 Question 82 Discussion

Actual exam question for Palo Alto Networks's PCCSE exam
Question #: 82
Topic #: 5
[All PCCSE Questions]

An administrator sees that a runtime audit has been generated for a host. The audit message is:

''Service postfix attempted to obtain capability SHELL by executing /bin/sh /usr/libexec/postfix/postfix- script.stop. Low severity audit, event is automatically added to the runtime model''

Which runtime host policy rule is the root cause for this runtime audit?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Pamella
1 months ago
I'm just going to go with C) Default rule that alerts on capabilities. Seems like the safest bet, and who knows, maybe the exam writers were feeling generous and decided to make this one a giveaway. *winks*
upvoted 0 times
Johnna
6 days ago
I agree, default rules are usually there for a reason.
upvoted 0 times
...
Doug
10 days ago
Yeah, that makes sense. It's better to go with the default rule in this case.
upvoted 0 times
...
Roosevelt
22 days ago
I think C) Default rule that alerts on capabilities is the most likely answer.
upvoted 0 times
...
...
Samuel
1 months ago
This question is a real head-scratcher! I bet the exam writers were chuckling to themselves when they came up with this one. Anyway, I'm going to go with D) Default rule that alerts on suspicious runtime behavior. Seems like the most logical choice to me.
upvoted 0 times
...
Aaron
1 months ago
Ah, I see! The audit message specifically mentions the postfix-script.stop file, which is likely a command used by the postfix service. So, the correct answer must be C) Default rule that alerts on capabilities.
upvoted 0 times
Paris
20 days ago
Exactly, the audit message clearly points to the postfix service attempting to obtain a specific capability.
upvoted 0 times
...
France
21 days ago
So, the default rule that alerts on capabilities would be triggered in this case.
upvoted 0 times
...
Erick
24 days ago
Yes, that makes sense. The postfix service was trying to obtain the SHELL capability.
upvoted 0 times
...
...
Odelia
2 months ago
Hmm, I'm not sure about this one. The audit message doesn't mention anything about file integrity or networking, so A) and B) don't seem to be the right answers. I'll have to think about this a little more.
upvoted 0 times
Bernardine
1 months ago
That makes sense, the audit message does mention the service attempting to obtain a capability.
upvoted 0 times
...
Novella
1 months ago
I think the answer might be C) Default rule that alerts on capabilities.
upvoted 0 times
...
...
Luz
3 months ago
The runtime audit message suggests that the postfix service tried to obtain the SHELL capability, which is a suspicious runtime behavior. So, I think the correct answer is D) Default rule that alerts on suspicious runtime behavior.
upvoted 0 times
Thurman
2 months ago
Yes, having proper runtime host policies can help prevent security breaches and unauthorized access.
upvoted 0 times
...
Gilma
2 months ago
It's important to have rules in place to catch these kinds of behaviors before they cause any harm.
upvoted 0 times
...
Eladia
2 months ago
I think the default rule that alerts on suspicious runtime behavior is the root cause for this audit message.
upvoted 0 times
...
Orville
2 months ago
I agree, the postfix service trying to obtain the SHELL capability does seem suspicious.
upvoted 0 times
...
...
Marguerita
3 months ago
I agree with Delisa, it seems like the default rule for capabilities is the root cause.
upvoted 0 times
...
Delisa
3 months ago
I believe it could be a default rule that alerts on capabilities.
upvoted 0 times
...
Miesha
3 months ago
I think the root cause is a custom rule for file integrity.
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