nerdexam
F5

101 · Question #264

The default staging-tightening period for attack signatures and wildcard entities is?

The correct answer is B. 7 days. The default staging-tightening period for attack signatures and wildcard entities in BIG-IP ASM is 7 days.

Section 4: Security Basics

Question

The default staging-tightening period for attack signatures and wildcard entities is?

Options

  • A5 days
  • B7 days
  • C10 days
  • D30 days

How the community answered

(25 responses)
  • B
    88% (22)
  • C
    4% (1)
  • D
    8% (2)

Why each option

The default staging-tightening period for attack signatures and wildcard entities in BIG-IP ASM is 7 days.

A5 days

5 days is not the default value; the system uses 7 days out of the box to allow adequate traffic sampling before tightening the policy.

B7 daysCorrect

BIG-IP ASM places newly added attack signatures and wildcard entities into staging for 7 days by default, during which violations are logged but not blocked, giving administrators time to review traffic patterns and validate the policy before enforcement begins.

C10 days

10 days exceeds the default staging period - while administrators can extend the period manually, the factory default is 7 days.

D30 days

30 days is far longer than the default 7-day period and would represent a custom configuration choice, not the out-of-the-box ASM default.

Concept tested: BIG-IP ASM default staging tightening period

Source: https://techdocs.f5.com/en-us/bigip-16-1-0/big-ip-asm-implementations/about-staging-and-enforcing-security-policy-components.html

Topics

#ASM staging#tightening period#attack signatures#wildcard entities

Community Discussion

No community discussion yet for this question.

Full 101 Practice