Broader security topics that touch the network without belonging to a single platform. Threat models, defensive design, and the trade-offs behind each control.
The bridge stayed up and ARP resolved the server, but ping and HTTP failed. In this FMC-managed FTDv home lab, one bridge member in the wrong Switched zone removed the intended deployed permits. Restoring its zone and deploying restored traffic.
An attached FMC file policy let a complete HTTP ZIP download pass because its rule selected FTP. Follow the saved rule, matching hashes, empty events, HTTP correction, and two verified ZIP resets in my home lab.
A ZIP block policy existed in FMC, but Allow-Web did not use it. This home lab follows the full download, empty File Events, policy attachment, and verified ZIP resets while PDF and TXT stayed intact.
A Snort 3 local rule set to Block still allowed HTTP in Detection mode. Follow the FMC event, real requests, and server captures, then change only Inspection Mode to Prevention and verify selective blocking.
An FMC twice NAT edit broke requests to both partner addresses. Follow real HTTP tests, UN-NAT phases, ASP drops and captures, then restore OLD-to-NEW destination translation and interface source PAT in the same rule.
A server’s inbound static NAT still worked, but its partner API calls reset. In my home lab, broad manual PAT before Auto NAT changed the outbound source to 10.42.20.1. Moving equivalent PAT after Auto NAT restored 10.42.20.5.
A disabled Allow-Web rule broke HTTP after deployment. FMC Deployment History restored traffic, but the saved policy stayed disabled. Follow the rollback, prove recovery, then reconcile FMC before the next deploy.
Curl timed out while FTD packet-tracer and FMC Unified Events said Allow. Inside/outside captures with Trace exposed the missing reply; restoring the server return route brought back the TCP handshake and HTTP 200.
A broad FMC prefilter Fastpath rule let client-b bypass an explicit ACP block and opened port 8080 for both clients. Real HTTP tests, packet-tracer and Unified Events show why Analyze restored access control in this home lab.
FMC deployed the route successfully and Unified Events said Allow, but HTTP timed out. Follow the FTD routing table, unanswered ARP, and packet-tracer drop to an unused next hop, then verify the fix through the real router.
A deliberate registration key mismatch produces FMC’s generic timeout. Follow the FTD tunnel evidence, clean registration, failed first deployment and successful retry, then build and test the FMC-managed forwarding baseline.
Fix an FDM access rule blocked by rule order. Follow real FTD packet-tracer, system support trace and acl-drop evidence, then verify recovery.