deviceposturecheck.com A guide by Firezone

Device posture checks before each private connection

A device posture check tests the security state of a device before the device reaches a private system. This guide explains the usual signals, the time at which a check runs, and the difference between device posture and device trust.

Read the Firezone device posture docsBook a demo

How a device posture check decides accessAn agent on a laptop reports the state of the device to an MDM or EDR provider. The policy engine syncs the records of the provider. The Firezone Client on the laptop asks the policy engine for a Resource. The policy engine tests the records, and then it permits a connection through the Gateway to the Resource.LaptopControl planeProvider cloudPrivate networkreportssyncrequestallowtrafficClientasks for a ResourceMDM or EDR agentreads device statePolicy enginetests posture rulesPosture providerholds device recordsGatewaycarries the trafficResourceproduction database
  1. An agent reports the state

    The MDM or EDR agent on the device sends signals such as disk encryption and firewall status to its provider.

  2. The records are synced

    The policy engine fetches the device records from each provider and matches them to Clients.

  3. The Client asks for access

    The policy engine tests the posture rules of the Policy against the record of that device.

  4. A healthy device connects

    If each applicable check passes, the Client gets a connection through the Gateway to that one Resource.

What device posture is

Device posture is the security state of a device at a point in time. A device posture check compares that state with a set of rules. If the device does not meet the rules, the access system refuses the connection.

Identity answers the question of who signs in. Device posture answers a different question. It tells you if the laptop or phone in use is safe enough for the system that the person wants.

The two answers are independent. A correct password and a second factor can come from a laptop with no disk encryption and an old operating system. A posture check stops that laptop before it reaches production data.

Most products make posture one condition of conditional access. The same rule can require a Group, a country, and a healthy device.

The signals that a posture check reads

A signal is one fact about the device. Most teams start with a small set.

  • Disk encryption. The disk is encrypted, so a stolen laptop does not expose its data.
  • Firewall. The host firewall is on.
  • OS version. The operating system has the current security updates.
  • Screen lock. The device locks after a short time and needs a passcode.
  • Endpoint protection. The EDR agent is installed, healthy, and reports no active threat.
  • MDM compliance. The device management system says that the device meets the company baseline.
  • Integrity. Secure boot is on, and a phone is not jailbroken or rooted.
  • Freshness. The provider heard from the device a short time ago.

Freshness is easy to forget. A record that says "encrypted" is of little use if the device last reported two months ago.

When the check runs, and who supplies the data

At sign-in or on each connection

Some products check posture one time, when the user signs in. The session then stays open for hours or days. If the user turns off the firewall after sign-in, the session continues.

Other products check posture each time the device opens a connection to a protected system. A change in the state of the device then has an effect at the next connection, not at the next sign-in.

Self-reported or attested

The source of a signal decides how much you can trust it.

  • Self-reported. The VPN client on the device reads the state and reports it. A person with administrator rights on the device can change the report.
  • Reported by a provider. A separate MDM or EDR agent reports to its own cloud service. The access system reads the record from that service, not from the device.
  • Attested. The device proves its identity with a key that hardware protects. The access system then knows that the record belongs to this device.

A provider record is only as good as the link between the record and the device. If the link is a serial number that the device reports, a different device can claim that serial number.

Device posture and device trust are different checks

People frequently use the two terms as if they were one. They answer different questions.

  • Device trust proves which device this is. A certificate from your MDM or PKI, with a private key that stays on the device, shows that your organization manages the device.
  • Device posture evaluates the state of that device. It tells you if the disk is encrypted and if the endpoint protection agent is healthy.

Each check has a gap that the other check closes. A managed device that is out of compliance keeps a valid certificate until the MDM revokes it. A healthy posture record gives little assurance if a different device can claim its identity.

Use the two checks together for sensitive systems. First prove the identity of the device. Then evaluate the state of the device.

Where posture checks go wrong

  • Stale records. The provider has old data because the device was offline. Add a freshness rule so that old evidence stops giving access.
  • Missing data. No provider reports the signal for some platform. Decide if missing data must fail the check. The safe answer is yes.
  • A broader rule. A strict rule protects the database, but an older rule gives the same people the full subnet. The broader rule wins.
  • One rule for all platforms. A rule about a jailbreak has no meaning for a Windows laptop. Apply each check only to the platforms where it has a meaning.
  • Lockouts. A new operating system release can make many devices fail on one day. Test each rule with a small group first.

How Firezone checks device posture

In Firezone, device posture is a part of a Policy. A Policy gives one Group access to one Resource. The posture rules of the Policy apply to each Client that uses it.

Where the data comes from

Firezone syncs device records from your MDM and EDR providers. The setup guide lists Microsoft Intune, Iru, Microsoft Defender for Endpoint, Santa, SentinelOne, and Sophos XDR. Firezone schedules a sync of each provider every two hours.

Firezone matches each record to a Client with the strongest shared identifier. It uses a certificate-attested MDM device ID first, then a certificate-attested serial number, then a serial number that the Client reports.

What you can check

The Simplified tab has ready-made checks such as disk encryption, firewall enabled, endpoint protection active, OS up to date, and MDM compliance. The JSON tab lets you select provider fields, set thresholds, and combine rules with and, or, and not.

The policy engine evaluates a Policy each time a Client tries to connect to a Resource. A check for a different platform is skipped. An applicable check fails when no provider supplies the data.

Limits to know

  • Device posture is on the Business and Enterprise plans. See pricing.
  • Posture reflects the records that Firezone last synced, so a change on the device is not visible immediately.
  • If a different Policy gives the same Group the same Resource with no posture rules, that Policy still gives access.
  • Firezone recommends that you set up device trust first and add the Require attestation condition. Without it, Firezone matches records with fields that the Client reports.

Posture checks in a legacy VPN, MDM compliance only, and Firezone

The three approaches read different data, and they apply the result at different levels.

Legacy VPNMDM compliance onlyFirezone
Source of the signalsThe VPN client on the deviceThe MDM agentRecords from MDM and EDR providers
When the check runsUsually at sign-inAt sign-in to an appAt each connection to a Resource
Different rules for each private systemPartialOne rule set for each tunnel profilePartialFor apps behind single sign-onYesPosture rules in each Policy
Covers SSH, databases, and other non-web trafficYesNoOnly apps that use the identity providerYesAny TCP, UDP, or ICMP traffic
EDR health as a signalPartialPartialThrough a partner integrationYes
Proof of device identityPartialMachine certificatesYesYesDevice trust with Require attestation
Works with no MDM or EDR in placeYesThe client collects basic signalsNoPartialOnly the Client version check

The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.

Common questions

What is a device posture check?

A device posture check compares the security state of a device with a set of rules before the device gets access. Typical rules require disk encryption, an active firewall, a current operating system, and a healthy endpoint protection agent.

What is the difference between device posture and device trust?

Device trust proves the identity of the device, usually with a certificate and a hardware-protected key. Device posture evaluates the state of the device, such as encryption and patch level. A trusted device can have bad posture, so sensitive systems need the two checks.

Is MDM compliance the same as device posture?

No. MDM compliance is one posture signal. It is the opinion of one management system about its own baseline. A posture check can also read signals from an EDR product, and it can apply different rules to different systems.

Does a posture check need an agent on the device?

Yes, some software must read the state of the device. That software can be the VPN client, an MDM agent, or an EDR agent. Firezone reads the records of your MDM and EDR providers, so it uses the agents that you already have.

How frequently must a device posture check run?

A check at sign-in only is weak, because a session can stay open for a long time. A check at each new connection is better. The data must also be fresh, so add a rule that the provider heard from the device recently.

Add a posture rule to one Policy first

Firezone is zero trust access built on WireGuard. Connect a posture provider, check the records of a test device, then add one check to the Policy for your most sensitive Resource.

See plans and pricingBook a demo