156-315.81.20 · Question #215
Identity Awareness allows the Security Administrator to configure network access based on which of the following?
The correct answer is D. Network location, identity of a user, and identity of a machine. See the full explanation below for the reasoning.
Question
Identity Awareness allows the Security Administrator to configure network access based on which of the following?
Options
- AName of the application, identity of the user, and identity of the machine
- BIdentity of the machine, username, and certificate
- CBrowser-Based Authentication, identity of a user, and network location
- DNetwork location, identity of a user, and identity of a machine
How the community answered
(28 responses)- A7% (2)
- B11% (3)
- C4% (1)
- D79% (22)
Community Discussion
8D is the correct answer. Identity Awareness in Check Point lets you build access rules around three things: where traffic is coming from (network location), who the user is (identity of a user), and what device they are on (identity of a machine). That combination is what makes it powerful, you can say "this user on this machine from this network segment gets access" instead of just relying on IP addresses alone. The other options throw in things like certificates or application names, which belong to other blades like Mobile Access or Application Control, not Identity Awareness specifically.
D is the right call here, and it lines up exactly with what I saw when we rolled out Identity Awareness on a customer deployment a few years back. The whole point of the feature is to move beyond just IP addresses and let you write policy around who the user is, what machine they are on, and where in the network that machine sits. In practice that meant we could finally write a rule that said "finance users on domain-joined machines coming from the corporate LAN get access to the payment segment" instead of just trusting a subnet. Option A trips people up because application identity is Threat Prevention and App Control territory, not Identity Awareness, and option C throws in Browser-Based Authentication as if it is a core dimension of the policy model rather than just one of the identity acquisition methods.
Thought A was right until I remembered location is the third pillar, not application.
Location matters for sure, but calling it a "pillar" is the exam's way of saying the policy basis for the traffic inspection rule, so application and service round out the match criteria alongside it.
D is the right pick here and honestly the way I remember it is that my senior walked me through the Identity Awareness policy screen and pointed out that the three things you are building access rules around are where the traffic is coming from, who is logged in, and what machine they are on, which maps exactly to network location, identity of a user, and identity of a machine. Option A trips people up because it throws in application name, but that is Application Control territory, not Identity Awareness. Option C sounds tempting because Browser-Based Authentication is a real thing in Check Point, but that is just one method for acquiring identity, it is not one of the access criteria you configure rules against. When I sat the actual exam I saw this question and almost went with C because I had just been reading about Captive Portal, but then I remembered my senior saying Identity Awareness is really about the three W's, who, what machine, and from where, and D was the only option that covered all three cleanly.
The "three W's" framing is solid, just worth reinforcing that the "from where" leg is really a network location object tied to a specific gateway interface or subnet, which matters when you are writing granular rules in a multi-site Maestro environment where you have many gateways sharing a policy and you need to scope rules to physical entry points, not just abstract zones.
D is correct. Identity Awareness ties access decisions to three dimensions, network location (the source network or subnet), the identity of the user (pulled via AD query, captive portal, or identity agent), and the identity of the machine (based on computer object or certificate), which together let you build Access Role objects that replace raw IP-based rules in the policy layer.
The machine identity piece is easy to overlook but it becomes critical the moment you have shared workstations or VDI environments where ten users might log in from the same IP over the course of a day.