Last Modified: Feb 18, 2025
Affected Product(s):
BIG-IP AFM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1
Opened: Sep 13, 2024 Severity: 3-Major Related Article:
K000140367
Protocol inspection in the security log profile is not activated/enabled when the first log profile has Protocol Inspection disabled and is already attached to the virtual server.
Inconsistency in configuration behavior.
1. Create the first security log profile (for example, enable a sub-module other than Protocol Inspection) and attach to a virtual server (VS). 2. Create the second security log profile with Protocol Inspection enabled, select a publisher and attach to the VS. 3. Event logs are not sent through the selected publisher which is not expected. Therefore, the protocol inspection log profile attached later to the virtual server is not effective.
Run the below command to detach the profiles from virtual server (VS) and attach the required log profile first. tmsh modify ltm virtual <VS Name> security-log-profiles none
None