Item | Description | Bug ID |
|---|---|---|
1. | Request of /v2/config/aw/SecurityEvents/ returned a false response. | DE75916 |
2. | The forensics search engine was not accurate. | DE74469 |
3. | Wildcard hostname (*nma.lt) worked incorrectly and caused false positive. | DE74667 |
4. | Session filter removed the cookie in passive mode. | DE74748 |
5. | There was no detailed information about a pattern. | DE74850 |
6. | AW version 7.6.11.51 nodes crashed without panic dumps. | DE75144 |
7. | Protected applications behind AppWall went down suddenly. | DE75232 |
8. | Under certain conditions, no explanation is provided in the Forensics API Security event. | DE75513 |
9. | Geo filter (ZZ) to display the Forensics logs for Private networks did not work. | DE75593 |
10. | In Forensics, the filter according to the Geo-Location did not work. | DE74346 |
11. | Failure to update the GEO file. | DE74563 |
12. | In API Protection, AppWall identifies parameters as "required" even when they are not in the uploaded file. | DE74572 |
13. | Failure occurs with unexpected headers in the server response. | DE74998 |
14. | AppWall Management REST for Allow-List misinterpreted a wildcard in the configuration. | DE75050 |