Share this article
Lessons from Vanta’s WebAuthn migration
In this ongoing series, you’ll hear directly from the teams keeping Vanta—and most importantly, our customers—secure. Today’s post by Rob Picard and Jess Chang on the Security team explains why and how we migrated to WebAuthn as the mandatory way to log into Okta.
Why we migrated to WebAuthn
Vanta’s mission is to secure the internet and protect consumer data—and as a company, security is always top of mind. To that end, the Vanta Security team recently took the step of transitioning our employees and apps to using WebAuthn devices as the mandatory way to log into Okta. Our primary motivation was our own mission, as well as the ever-present issue of phishing, increasing adoption of WebAuthn, and the growing implementation of passkeys with platform authenticators.
In the past, it was common for organizations to look to passwordless authentication by deploying YubiKeys, or hardware authentication devices. However, most computers and phones deployed today have built-in FIDO2 keys as platform authenticators. This applies to all devices in use at Vanta. With Okta in use as our identity provider, we were able to rely on Okta’s built-in functionality to enforce enrollment of employee laptops and phones.
Our migration strategy
At Vanta, we onboarded every employee onto biometric authentication over the course of a month with minimal disruption, clear resources, and individual reminders. In partnership with our Enterprise Engineering team, we implemented the change by providing employee resources and a lightweight survey to track employee migration.
Specifically, employees were asked to add biometric keys to Okta on both their laptop and their phone, then submit a short form to indicate their readiness. We set up automation to then add all users who’d submitted the survey into a WebAuthn enforcement group.
For any edge cases, we set up a separate group for employees who requested an exception for any reason and opted to automatically grant exceptions for all requests to prevent undue delay.
In terms of applications, we tested each separately to determine which couldn’t support WebAuthn and created an application exception group. While this mostly went seamlessly, we ran into a few issues with managed Chrome browsers since a few employees had passkeys which were tied to their old Chrome profiles. This resulted in a handful of employees being locked out of their Chrome profile and therefore unable to log in using their passkey, which required extra support.
Communication and resources to support employees
First, we communicated our planned WebAuthn rollout to our leadership team, followed by all managers. Our goal was to help set expectations for their organizations and teams and get the ball rolling with migrations—especially from those who tend to have the busiest schedules at Vanta.
To set up our employees for success, we created and shared a range of initial resources including the following:
- Short video with enrollment instructions for both laptop and phone
- Article with details on biometric authentication, steps for setup, and how to get help
- Slack channel for dedicated support
- Office hours for hands-on support from the team
As we approached the deadline for migration, we set up automated Slack notifications for employees with friendly reminders and guidance for how to add biometric keys, and also followed up with a handful of employees manually if they had questions.
Edge cases and solutions
In the process of migrating to WebAuthn across the company, we ran into edge cases for employee migration including the following:
- Discomfort with enabling FaceID/facial recognition for biometric authentication
- Biometric authentication broken on device
- Employee on extended leave (e.g. parental, medical) or time-off
- Use of unsupported browsers (e.g. Firefox) or multiple browsers
Given that each of these cases must be handled differently depending on the circumstances, we opted to set up a trackable, documented exception workflow that required a clear explanation using our internal ticketing system. For these users, we required a non-biometric, phishing-resistant form of multifactor authentication (MFA) and slowly moved users off the exception group when possible.
While we hit a few small bumps in the road, our overall migration went smoothly and we were able to migrate 95% of our employees and 90% of applications within the span of a month. All exceptions are documented and officially reviewed. This change not only provides our employees with a seamless authentication experience, but also helps us keep Vanta more secure.
Tips for migration
While plans for migrating to WebAuthn will differ between companies and teams, here are a few lessons we learned:
- Clarity over complexity: As Security professionals, remember to use terms that are accessible and understandable to all employees, especially when you’d like them to take action. For instance, we opted to refer to this project as the rollout of biometric authenticators instead of referring to FIDO2 or WebAuthn, terms which could have been more nuanced to grasp.
- Always over-communicate: Your employees are extremely busy, and it’s important to emphasize and over-communicate action items—then deliver quickly and answer questions quickly to be thoughtful of their time.
- Eliminate red tape: Find ways to prioritize employee experience and eliminate red tape, where possible. We opted to automatically grant exceptions upon request to help enable our employees to do their jobs. While any risk is a risk, the marginal increase in the risk of one individual not being behind biometric authentication is relatively minimal.
- Bake in extra time: Remember that your employees are busy and even with the best of intentions, your deadlines may slip. Communicate an earlier deadline in order to build in buffer time, especially if you’re approaching a holiday or a particularly busy time for your organization.
- Always be prepared: Even with the best of preparation and resources, you may run into cases where users misunderstand your instructions. Be prepared with extra resources, patience, and the reminder that we’re all trying our best.
Looking for more resources and best practices from Vanta's Security team? Read Our approach to threat modeling next!
Determine whether the GDPR applies to you and if so, if you are a processor or controller (or both)
Do you sell goods or service in the EU or UK?
Do you sell goods or services to EU businesses, consumers, or both?
Do you have employees in the EU or UK?
Do persons from the EU or UK visit your website?
Do you monitor the behavior of persons within the EU?
Create a Data Map by taking the following actions
Identify and document every system (i.e. database, application, or vendor) which stores or processes EU or UK based personally identifiable information (PII)
Document the retention periods for PII in each system
Determine whether you collect, store, or process “special categories” of data
Determine whether your Data Map meets the requirements for Records of Processing Activities (Art. 30)
Determine whether your Data Map includes the following information about processing activities carried out by vendors on your behalf
Determine your grounds for processing data
For each category of data and system/application have you determined the lawful basis for processing based on one of the following conditions?
Take inventory of current customer and vendor contracts to confirm new GDPR-required flow-down provisions are included
Review all customer contracts to determine that they have appropriate contract language (i.e. Data Protection Addendums with Standard Contractual Clauses)
Review all in-scope vendor contracts to determine that they have appropriate contract language (i.e. Data Protection Addendums with Standard Contractual Clauses)
Have you performed a risk assessment on vendors who are processing your PII?
Determine if you need to do a Data Protection Impact Assessment
Is your data processing taking into account the nature, scope, context, and purposes of the processing, likely to result in a high risk to the rights and freedoms of natural persons?
Review product and service design (including your website or app) to ensure privacy notice links, marketing consents, and other requirements are integrated
Does the notice to the data subject include the following items?
Does the notice also include the following items?
Do you have a mechanism for persons to change or withdraw consent?
Update internal privacy policies to comply with notification obligations
Update internal privacy notices for EU employees
Determine if you need to appoint a Data Protection Officer, and appoint one if needed
Have you determined whether or not you must designate a Data Protection Officer (DPO) based on one of the following conditions (Art. 37)?
If you export data from the EU, consider if you need a compliance mechanism to cover the data transfer, such as model clauses
If you transfer, store, or process data outside the EU or UK, have you identified your legal basis for the data transfer (note: most likely covered by the Standard Contractual Clauses)
Have you performed and documented a Transfer Impact Assessment (TIA)?
Confirm you are complying with other data subject rights (i.e. aside from notification)
Do you have a defined process for timely response to Data Subject Access Requests (DSAR) (i.e. requests for information, modification or deletion of PII)?
Are you able to provide the subject information in a concise, transparent, intelligible and easily accessible form, using clear and plain language?
Do you have a process for correcting or deleting data when requested?
Do you have an internal policy regarding a Compelled Disclosure from Law Enforcement?
Determine if you need to appoint an EU-based representative, and appoint one if needed
Have you appointed an EU Representative or determined that an EU Representative is not needed based on one of the following conditions?
If operating in more than one EU state, identify a lead Data Protection Authority (DPA)
Do you operate in more than one EU state?
If so, have you designated the Supervisory Authority of the main establishment to act as your Lead Supervisory Authority?
Implement Employee Trainings to Demonstrate Compliance with GDPR Principles and Data Subject Rights
Have you provided appropriate Security Awareness and Privacy training to your staff?
Update internal procedures and policies to ensure you can comply with data breach response requirements
Have you created and implemented an Incident Response Plan which included procedures for reporting a breach to EU and UK Data Subjects as well as appropriate Data Authorities?
Do breach reporting policies comply with all prescribed timelines and include all recipients i.e. authorities, controllers, and data subjects?
Implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk
Have you implemented encryption of PII at rest and in transit?
Have you implemented pseudonymization?
Have you implemented appropriate physical security controls?
Have you implemented information security policies and procedures?
Can you access EU or UK PII data in the clear?
Do your technical and organizational measure ensure that, by default, only personal data which are necessary for each specific purpose of the processing are processed?
Develop a roadmap for successful implementation of an ISMS and ISO 27001 certification
Implement Plan, Do, Check, Act (PDCA) process to recognize challenges and identify gaps for remediation
Consider ISO 27001 certification costs relative to org size and number of employees
Clearly define scope of work to plan certification time to completion
Select an ISO 27001 auditor
Set the scope of your organization’s ISMS
Decide which business areas are covered by the ISMS and which are out of scope
Consider additional security controls for business processes that are required to pass ISMS-protected information across the trust boundary
Inform stakeholders regarding scope of the ISMS
Establish an ISMS governing body
Build a governance team with management oversight
Incorporate key members of top management, e.g. senior leadership and executive management with responsibility for strategy and resource allocation
Conduct an inventory of information assets
Consider all assets where information is stored, processed, and accessible
- Record information assets: data and people
- Record physical assets: laptops, servers, and physical building locations
- Record intangible assets: intellectual property, brand, and reputation
Assign to each asset a classification and owner responsible for ensuring the asset is appropriately inventoried, classified, protected, and handled
Execute a risk assessment
Establish and document a risk-management framework to ensure consistency
Identify scenarios in which information, systems, or services could be compromised
Determine likelihood or frequency with which these scenarios could occur
Evaluate potential impact of each scenario on confidentiality, integrity, or availability of information, systems, and services
Rank risk scenarios based on overall risk to the organization’s objectives
Develop a risk register
Record and manage your organization’s risks
Summarize each identified risk
Indicate the impact and likelihood of each risk
Document a risk treatment plan
Design a response for each risk (Risk Treatment)
Assign an accountable owner to each identified risk
Assign risk mitigation activity owners
Establish target dates for completion of risk treatment activities
Complete the Statement of Applicability worksheet
Review 114 controls of Annex A of ISO 27001 standard
Select controls to address identified risks
Complete the Statement of Applicability listing all Annex A controls, justifying inclusion or exclusion of each control in the ISMS implementation
Continuously assess and manage risk
Build a framework for establishing, implementing, maintaining, and continually improving the ISMS
Include information or references to supporting documentation regarding:
- Information Security Objectives
- Leadership and Commitment
- Roles, Responsibilities, and Authorities
- Approach to Assessing and Treating Risk
- Control of Documented Information
- Internal Audit
- Management Review
- Corrective Action and Continual Improvement
- Policy Violations
Assemble required documents and records
Review ISO 27001 Required Documents and Records list
Customize policy templates with organization-specific policies, process, and language
Establish employee training and awareness programs
Conduct regular trainings to ensure awareness of new policies and procedures
Define expectations for personnel regarding their role in ISMS maintenance
Train personnel on common threats facing your organization and how to respond
Establish disciplinary or sanctions policies or processes for personnel found out of compliance with information security requirements
Perform an internal audit
Allocate internal resources with necessary competencies who are independent of ISMS development and maintenance, or engage an independent third party
Verify conformance with requirements from Annex A deemed applicable in your ISMS's Statement of Applicability
Share internal audit results, including nonconformities, with the ISMS governing body and senior management
Address identified issues before proceeding with the external audit
Undergo external audit of ISMS to obtain ISO 27001 certification
Engage an independent ISO 27001 auditor
Conduct Stage 1 Audit consisting of an extensive documentation review; obtain feedback regarding readiness to move to Stage 2 Audit
Conduct Stage 2 Audit consisting of tests performed on the ISMS to ensure proper design, implementation, and ongoing functionality; evaluate fairness, suitability, and effective implementation and operation of controls
Address any nonconformities
Ensure that all requirements of the ISO 27001 standard are being addressed
Ensure org is following processes that it has specified and documented
Ensure org is upholding contractual requirements with third parties
Address specific nonconformities identified by the ISO 27001 auditor
Receive auditor’s formal validation following resolution of nonconformities
Conduct regular management reviews
Plan reviews at least once per year; consider a quarterly review cycle
Ensure the ISMS and its objectives continue to remain appropriate and effective
Ensure that senior management remains informed
Ensure adjustments to address risks or deficiencies can be promptly implemented
Calendar ISO 27001 audit schedule and surveillance audit schedules
Perform a full ISO 27001 audit once every three years
Prepare to perform surveillance audits in the second and third years of the Certification Cycle
Consider streamlining ISO 27001 certification with automation
Transform manual data collection and observation processes into automated and continuous system monitoring
Identify and close any gaps in ISMS implementation in a timely manner
Download this checklist for easy referenceDownload Now
Determine which annual audits and assessments are required for your company
Perform a readiness assessment and evaluate your security against HIPAA requirements
Review the U.S. Dept of Health and Human Services Office for Civil Rights Audit Protocol
Conduct required HIPAA compliance audits and assessments
Perform and document ongoing technical and non-technical evaluations, internally or in partnership with a third-party security and compliance team like Vanta
Document your plans and put them into action
Document every step of building, implementing, and assessing your compliance program
Vanta’s automated compliance reporting can streamline planning and documentation
Appoint a security and compliance point person in your company
Designate an employee as your HIPAA Compliance Officer
Schedule annual HIPAA training for all employees
Distribute HIPAA policies and procedures and ensure staff read and attest to their review
Document employee trainings and other compliance activities
Thoroughly document employee training processes, activities, and attestations
Establish and communicate clear breach report processes
to all employees
Ensure that staff understand what constitutes a HIPAA breach, and how to report a breach
Implement systems to track security incidents, and to document and report all breaches
Institute an annual review process
Annually assess compliance activities against theHIPAA Rules and updates to HIPAA
Continuously assess and manage risk
Build a year-round risk management program and integrate continuous monitoring
Understand the ins and outs of HIPAA compliance— and the costs of noncompliance
Download this checklist for easy referenceDownload Now
FEATURED VANTA RESOURCE
The ultimate guide to scaling your compliance program
Learn how to scale, manage, and optimize alongside your business goals.