12/02/2024 | News release | Distributed by Public on 12/02/2024 13:34
Charlotte Wylie, SVP and Deputy Chief Security Officer at Okta, leads Okta's technical cybersecurity services. This includes overseeing Okta's global engineering teams to enhance the company's security posture and programs that support its over 19,000 customers. Charlotte has an extensive background in the delivery of security transformation programs and leading global engineering teams, creating value through enhancing security posture aligned with business goals for large corporations. Recognizing that many other organizations face some of the same challenges and threats, we asked Charlotte to share some thoughts about what it takes to verify the Identity of remote workers. |
Remote Identity verification is growing in difficulty, but also in importance. Deepfakes are on the rise. They're increasingly hard to distinguish from reality, and increasingly harmful to security as a result. So how do you verify an employee is who they say they are when youcan'tphysically verify them?
As a large enterprise with operations and offices around the globe, Okta has many remote workers connecting to its systems (using hardened devices) from home offices and other locations. Two of the more common remote-working questions I get asked are:
Let's explore some best practices that organizations can use in these scenarios, based on what we've put in place at Okta, and what I've seen work in the industry as a whole.
Before we dive in, I want to stress that none of what I'm saying here is a substitute for a strong insider threatprogram, combining physical security, personnel awareness, and information-centric principles. Rather, these should all be regarded as complementary approaches to building and maintaining a strong security posture, existing under a broader security culture.
While the risks associated with exclusively remote recruiting and hiring are not new, they came to the fore in July 2024 when Stu Sjouwerman, CEO and founder of security firm KnowBe4, posted a blog titled How a North Korean Fake IT Worker Tried to Infiltrate Us.
Sjouwerman's post details how KnowBe4 unwittingly hired a North Korean hacker - who used "a valid but stolen U.S.-based identity" - into a software engineer role. Almost immediately upon booting up their newly provided corporate laptop, the hacker began to load malware. Fortunately, KnowBe4's security controls detected the abuse, and the incident was contained before the hacker caused damage.
KnowBe4's experience isn't an isolated event. In fact, three U.S. government agencies issued a joint advisory in 2022warning that North Korean IT workers were attempting to use Identity fraud to secure employment and gain access to sensitive information. The FBI published additional guidancein 2023, and the UK's Office of Financial Sanctions Implementation issued a similar warningwith even more detail.
The risk posed by North Korean hackers is serious and should not be underestimated, but Identity fraud extends beyond individuals acting on behalf of regimes. Sometimes, applicants use proxies to apply for a job - the person who shows up to work is not the same person the company interviewed.
Whatever the case, Identity fraud puts the company at risk.
Unfortunately, there's no simple fix for combating Identity fraud. If there were, organizations wouldn't be facing this challenge.
In practice, strengthening your security defenses takes a multi-layered approach involving a combination of people, processes, and technology. In addition to the suggestions that follow, I recommend reading the government advisories linked in the previous section.
Start with your people:
Build the processes to strengthen your security posture:
Adopt the technology to support your people and processes:
Now to address the second question: How do we verify the identity of a remote team member at some later point?
For context, some threat actors take advantage of vulnerable account recovery flows to access protected IT environments, often by phoning an organization's help desk and pretending to be a legitimate member of the workforce.
Usually, such threat actors exploit account recovery flows that rely on single authentication factors:
To combat these threats, we've leveraged our own tools and our workforce-wide implementation of YubiKeys to implement caller identity verification that's phishing-resistant, auditable, and user-friendly for help desk agents and legitimate callers.
Organizations that haven't implemented offline security keys can still introduce safeguards to help verify caller identity. For example, Okta Workflowsmakes it possible to largely automate a caller Identity verification process using Okta-enrolled authentication factors, including:
It's important toregularly revisit your training and proceduresfor verifying the identities of your remote workers, especially in the context of the most current tactics, techniques, and procedures employed by threat actors. Adversaries are highly motivated to find workarounds to your defenses, and a safeguard that was highly effective yesterday might not be as reliable tomorrow.
While technology can play a role, especially for phishing-resistant authentication, people and processes are also essential. Maximizing our protection against Identity fraud requires all three elements working in concert.
Finally, none of the above eliminates the need for an insider threatprogram, which complements the practices outlined above by helping to discover threats that made their way through your hiring filters (and by detecting the unfortunate scenario of a good employee gone bad).
If you want to learn more about securing your whole workforce, including contractors, vendors, and other third parties, read my article The weakest link: Securing your extended workforce.