FortiWeb Lesson 11: Attack Logs and Evidence-Based Troubleshooting
FORTIWEB CLASSROOM • LESSON 11
Level: Intermediate · Study and lab: 60 minutes
Instructor: Harpreet Singh Virdi, CISSP, CCSP
FortiWeb course guide · FortiWeb training block
Investigate one request at a time
A user reports that checkout failed. Before editing security settings, determine whether FortiWeb, the application, or another component rejected the request. A status code and a screenshot are useful starting points, but they do not identify the cause.
Know the log families
Attack logs describe security detections. Traffic logs help explain requests and responses when enabled. Event logs describe system or administrative activity. Storage, severity filters, destinations, and feature settings determine what is available. An empty view does not prove a request was allowed.
Read an attack event in order
- Confirm time, timezone, device, hostname, URL, method, and server policy.
- Read the action actually taken.
- Identify the attack type, rule, signature ID, or constraint involved.
- Inspect the matched input location and available sanitized context.
- Correlate with client behavior, traffic records, and origin logs.
Payload capture can expose tokens, cookies, passwords, and submitted data. Enable only the retention needed for the investigation, use the available sensitivity controls, and restrict access. Captured payloads can also be truncated; absence of bytes from a captured fragment is not proof they were absent from the request.
Guided lab
- Verify that lab logging is enabled and the intended destination is functioning.
- Send a normal request and a deterministic request triggering your test access rule.
- Record the timestamp and application path using synthetic values.
- Open the attack-log viewer and filter to the relevant time, policy, and URL.
- Explain the match and response in two sentences.
- Generate a harmless application-originated error and compare its evidence with the FortiWeb-generated response.
- Remove unnecessary packet capture and confirm the planned logging configuration remains.
Expected result: you can attribute the two failures correctly and state what the logs do not establish. If no event appears, check traffic selection, logging status, filters, retention, destination health, and clock alignment.
Use dashboards carefully
Summaries help find repeated patterns, but counts alone do not diagnose an individual request. Drill into the event. FortiView analysis can help group matching characteristics for tuning; review the actual requests and requirements before accepting an exception.
Knowledge check
A request has a high severity label. Does that prove successful exploitation?
Instructor answer
No. Severity helps prioritize investigation. Establish the match, action, application vulnerability, and outcome with supporting evidence.
Official reading
Independent training, not affiliated with Fortinet. Examples use an authorized isolated lab with synthetic data. The lab steps and expected outcomes have not been executed on a FortiWeb appliance for this publication. Firmware, platform, operating mode, licensing, and subscriptions affect behavior; follow the documentation for your exact build. References use 8.0.x examples and do not constitute an upgrade recommendation.
← Previous FortiWeb lesson · FortiWeb course guide · Next FortiWeb lesson →
Comments
Post a Comment