You are assisting a company with designing role-based access control policies on HPE Aruba Networking AOS-10 gateways. The security policy dictates that traffic originating from authenticated corporate user roles must be inspected statefully, allowing client-initiated outbound flows to the data center while strictly dropping any unsolicited inbound connection attempts initiated from data center servers back toward the clients.
What design principle ensures this traffic flow behavior?
In HPE Aruba Networking AOS-10 architectures, the Policy Enforcement Firewall (PEF) is an application-aware, stateful Layer 4--7 firewall embedded directly within the datapath of gateways and access points.
When an Access Control Entry (ACE) is defined within a user role's session ACL (for example, permitting traffic with user host 10.20.1.50 svc-https permit), the PEF datapath dynamically constructs a bidirectional stateful session flow entry in its hardware session table upon observing the client's initial TCP SYN or UDP packet.
Because the firewall tracks protocol states (including TCP sequence/acknowledgment numbers and UDP pseudo-sessions), it automatically permits corresponding return traffic returning from the destination server back to the client. Crucially, this stateful tracking is unidirectional with respect to session establishment: external hosts, including data center servers, cannot initiate new, unsolicited connections toward the client because no matching stateful session exists in the reverse direction. Engineers do not need to configure inverse rules, inspect raw TCP ACK flags, or deploy secondary firewalls, as PEF enforces this stateful isolation by default.



