TL;DR: Remote work security is now a distributed identity and endpoint problem, not a perimeter problem: the article shows how phishing, credential reuse, unmanaged devices, shadow IT, and misconfigured VPNs expand attack surface while weakening compliance, according to Netwrix. The practical lesson is that Zero Trust, just-in-time privilege, and continuous visibility have become baseline controls, not optional hardening.
NHIMG editorial — based on content published by Netwrix: Remote work security, the complete guide to securing the digital workspace
By the numbers:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
- Only 5.7% of organisations have full visibility into their service accounts.
Questions worth separating out
Q: How should security teams secure remote access without relying on VPN trust alone?
A: Use VPN as transport protection, not as the trust decision.
Q: Why do remote workers create more risk for identity and access management programmes?
A: Remote work expands the number of places where credentials, devices, and data can be compromised.
Q: What do organisations get wrong about BYOD in remote work security?
A: They often treat BYOD as a cost decision instead of an access-control decision.
Practitioner guidance
- Harden remote access with conditional trust checks Require identity verification, device health, and location-aware policy before granting access to sensitive applications.
- Eliminate standing privilege for remote users and admins Use just-in-time elevation for administrative tasks, then revoke the privilege immediately after the session closes.
- Enforce endpoint baselines before access is allowed Block access from devices that lack encryption, patch currency, or endpoint protection, and use remote wipe on lost or stolen assets that still cache credentials.
What's in the full article
Netwrix's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step recommendations for securing home networks, BYOD endpoints, and remote access paths.
- Product-specific coverage of endpoint protection, privilege controls, and audit reporting across the Netwrix stack.
- More detailed explanations of remote worker training, policy enforcement, and compliance-oriented control options.
- Expanded FAQ guidance on VPN limitations, patching cadence, and personal device risk management.
👉 Read Netwrix's guide to remote work security and identity risk →
Remote work security: are your identity controls keeping up?
Explore further
Remote work security is fundamentally an identity governance problem, not just an endpoint problem. The article is strongest when it connects device posture, authentication, and data movement into one control plane. That is the right framing for modern IAM because a remote session is only as trustworthy as the identity behind it and the endpoint carrying it. Practitioners should treat remote work as a governance domain that spans human identity, machine credentials, and privileged access.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
A question worth separating out:
Q: Who is accountable when remote work access fails and data is exposed?
A: Accountability usually spans IAM, endpoint management, security operations, and the business owner of the data. Remote work failures are rarely caused by one control alone. The right governance model assigns ownership for identity assurance, device posture, privileged access, and data movement so gaps are not left between teams.
👉 Read our full editorial: Remote work security exposes identity and endpoint control gaps