INSURANCE

Verify independent agent device security without MDM

Carriers need a way to enforce and prove device security for agents who access carrier systems from personal devices. Ensure verifies agent devices at login and creates exportable evidence for NYDFS and internal audit.

NYDFS Part 500No MDM RequiredAgent Self-Install

Independent agents are a large unmanaged workforce

Agents drive distribution, but carriers do not control their devices. That creates a gap between policy requirements and what security teams can actually enforce at access time.

No carrier can practically enroll agents in MDM — agents won't accept it, and no single carrier has the right to manage a device shared across competitor relationships.

NYDFS Part 500: Section-by-section mapping

What examiners ask for is not just policy language. They ask how you enforce controls and what evidence you can produce.

§500.7Access Privileges
What examiners expect

Documented controls on who and what devices can access your systems.

Common gap

An agent signs in from any device, and no posture verification occurs. Access is gated by identity only.

What you can document

Device posture verification at every login. Access denied if the device fails. Evidence of every check.

§500.11Third-party security policy
What examiners expect

You have a policy and you can show it is enforced.

Common gap

Policy exists, but enforcement is manual or based on agent self-attestation.

What you can document

Your policy is enforced at every login. Evidence is created automatically.

§500.12Multi-factor authentication
What examiners expect

MFA for all external access to nonpublic information.

Common gap

MFA is enforced, but device posture is not checked alongside it. An agent with valid credentials on a compromised device passes MFA.

What you can document

Device posture check layered with your existing MFA through Conditional Access. Both identity and device are verified.

§500.13Asset inventory
What examiners expect

You can account for devices that access your systems.

Common gap

Inventory covers company devices only. Agent devices are invisible.

What you can document

Every verified device is recorded in an exportable inventory.

§500.14Third-Party Security Policy
What examiners expect

Documented security requirements for third-party access and evidence of enforcement.

Common gap

Agents are required to attest to device security annually. No real-time verification exists.

What you can document

Real-time enforcement of device security requirements at every access event. Continuous evidence, not annual attestation.

§500.17Annual attestation
What examiners expect

Your attestation is backed by evidence.

Common gap

Third-party device access is a known weak spot.

What you can document

Reports support your claims across policy, enforcement, inventory, and monitoring.

Agents self-install. Carrier IT does not provision devices.

Carriers send an enrollment link. Agents install the lightweight agent on their device and are checked at next login. If a device fails, they get clear fix steps.

For carriers with 10,000+ agents, self-enrollment eliminates the IT provisioning bottleneck entirely.

What exam evidence looks like

audit-log — live
2026-02-14 08:45:12AGT-2291-W[email protected]
pass
macOS 15.3FileVault:ON
2026-02-14 08:47:33AGT-5504-M[email protected]
fail
Win11 24H2BitLocker:OFF
2026-02-14 08:52:01AGT-5504-M[email protected]
remediated
Win11 24H2BitLocker:ON
NYDFS Part 500 Mapping
§500.7Access Privileges
§500.12Multi-Factor Auth
§500.14Monitoring & Testing

Want to see the technical verification flow?

See How It Works

See how Ensure fits your agent access model and NYDFS requirements

Review a sample audit pack or book a compliance demo for insurance carrier workflows.