Share this article
How we scaled our security culture at Vanta
Accelerating security solutions for small businesses Tagore offers strategic services to small businesses. | A partnership that can scale Tagore prioritized finding a managed compliance partner with an established product, dedicated support team, and rapid release rate. | Standing out from competitors Tagore's partnership with Vanta enhances its strategic focus and deepens client value, creating differentiation in a competitive market. |
Security is at the heart of what we do at Vanta—helping our customers improve their security and compliance posture starts with our own. Our team’s mission is to ensure that Vanta is a trusted and trustworthy steward of customer data.
At Vanta, we believe that nurturing and scaling our security culture is one of the most powerful ways to achieve our mission. We define security culture as the norms, behaviors, and attitudes around security. We look at our security culture through the following three primary tenets with the belief that these are distinct:
- Vanta staff cares about security (beliefs and values)
- Vanta staff understands their responsibilities when it comes to keeping the company secure (knowledge)
- Vanta staff reaches out with security questions and to ask for guidance (behaviors)
Why three tenets? An individual can care about security and understand their responsibilities, but make a misguided security decision if they opt to not ask for guidance at a critical junction in their project. An employee who doesn’t care about security will likely not understand their responsibilities, and is even less likely to reach out to ask for security guidance. A healthy security culture requires all three tenets operating in tandem to sustain itself.
Why security culture matters
While there are many reasons why security culture matters, one thing in particular stands out to us—which is that establishing a strong security culture enables the Security team to have greater leverage and be more impactful.
By equipping and empowering teams to partner with the Security team or even address security issues on their own, establishing a strong security culture allows the team to multiply their impact—even with the same resources. For example, at Vanta we partner closely with our Platform team within the Engineering organization through regular meetings that address problems before they even arise. Not only does this help broaden our team’s impact, but also helps avoid creating issues that will surface later.
Security culture interfaces and principles
You might be wondering how to define and scale your security culture. You may have a function devoted to human risk, security culture, or even security education or generalists on your security team who can lend a hand.
At Vanta, we have a shared responsibility model for nurturing our security culture. We group our guiding principles into two categories depending on whether an employee is interacting with our Security team or tooling we manage, and we work to nurture and improve these consistently:
- Human touchpoints: Between the Security team and Vanta’s staff
- Tooling touchpoints: Between Vanta’s staff and the tooling or controls built by the Security team
While related, these two distinct touchpoints have different principles that guide our approach to consistently improving our security culture and our overall security strategy. We’ve shared these team principles below with the hopes that these will be helpful as you look to build and scale your own security culture as well.
Human touchpoint principles: Between Vanta’s Security team and staff
1. Culture of yes: We strive to nurture a culture where partner teams come to us collaboratively to work toward solutions, instead of a culture of fear or one where the Security team consistently says no. This means we must cultivate a responsive, supportive, and judgment-free environment that encourages active engagement with Security. We invite feedback through a biannual, company wide survey that measures friction against security controls and guidance and regularly remind employees how to get help from the Security team. In addition, we operate in a blameless environment that focuses on identifying root causes and solutions.
2. Guardrails are better than gates: Our goal is to help our partner teams by providing guidance and solutions that help meet their needs while not slowing them down. At times, we recognize that this requires imparting a significant amount of trust on our partner teams. Developer experience and productivity are critical to making our systems and processes more secure. We should favor guardrails that make the right and secure thing easy to do, instead of gates that add friction and toil.
3. Be predictable and consistent: In providing guidance, we always seek to provide practical, consistent, and clear guidance from a first principles approach. This means that we’re also transparent when we don’t know what the right answer is—and work closely with teammates to connect our technical expertise in security with their domain expertise. After all, we can’t be successful without the deep domain expertise of our partner teams. In addition, when we’re asked for help, it’s important for us to share clear next steps and a timeline with the requester so they know what to expect and when.
4. Security is everyone’s responsibility (and can be fun!): While Vanta certainly has a dedicated Security team (us!), we also find ways to create fun, inviting, and accessible ways to learn about security—whether related to Vanta and our work or to our personal lives outside work. Our Security team runs a monthly Capture the Flag (CTF) open to all employees, and also maintains an open Slack channel for articles and discussions on a range of security topics.
In addition, we share monthly company-wide security updates on what we’re working on and why, as well as threat briefings on an as-needed basis for any potential threats relevant to Vanta or our staff. On a quarterly basis, we also share our top risks and priorities, which helps inform teams and assists in their planning and prioritization. Lastly, as a security company, having clear support from Vanta’s leadership team has also helped emphasize the importance of our internal security initiatives—such as our MDM rollout and migration to WebAuthn.
5. Build a security mindset from the start: To ensure our staff cares about security, understands their responsibilities in keeping Vanta secure, and knows how to ask security questions and get guidance from Day 1, we introduce security at the start—with general onboarding for all employees as well as security training for developers. In addition, we pair our dynamic onboarding content with Vanta’s in-product security and privacy training, and provide regular training on an as-needed basis.
Tooling touchpoint principles: Between Vanta’s staff and tooling
1. Prioritize developer experience: One of the primary goals behind our biannual internal Security team survey is to understand and address any potential points of friction, particularly in our developer experience. If the developer experience is suboptimal because of security controls or otherwise, it will materially impact our overall security culture and lead to decreased engagements with our team. What we build is most readily adopted when it fits into the workflows our developers use—and doesn’t cause additional friction.
2. Shift security left: Embracing this emerging industry principle, we put interfaces in the paths and toolkit of engineers to help keep Vanta secure while also cultivating a healthy relationship with our developers. Our highest leverage efforts are in pushing controls closer to our teammates, while they’re building, designing, and coding. This gives quicker feedback cycles and helps catch security bugs early on in the software development process.
3. Minimize alert fatigue: It’s well-established that tooling with overly-sensitive or poorly-defined monitoring and alerting protocols can lead to alert fatigue and easy dismissal of alerts, even when these alerts may be important. This can create a negative security culture of quickly clicking through a security speed bump versus a culture of paying attention. To combat this, we consistently work to fine-tune our monitoring and alerting and adjust on a continual basis.
4. Secure by default: To help create the right guardrails for our employees and environment, we opt for settings and controls that balance the right levels of security and productivity—and provide clear rationale and guidance for employees where needed.
Additional guidance: Always be automating & documenting
Two additional principles we love internally on Vanta’s Security team include always be automating and always be documenting. These two principles help ensure we’re building repeatable processes, improving our overall team bandwidth and consistency, and creating ways for us to continue to evolve alongside Vanta’s business needs.
As an example, the Security team maintains a decision log that helps us understand any important internal decisions that might help us evaluate future stance and direction. This helps ensure we’re able to provide consistent, principle-based guidance as we grow and scale, and reference prior decisions where relevant.
Lastly, we recognize that every company and team has their own approach to building and nurturing security culture—and we hope that sharing our internal principles and perspectives can help you decide how to approach defining and scaling your own.
“
“
Determine if you need to comply with GDPR
Not all organizations are legally required to comply with the GDPR, so it’s important to know how this law applies to your organization. Consider the following:
Do you sell goods or services 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?
If any of the above statements apply to your business, you’ll need to be GDPR compliant.
Document the personal data you process
Because GDPR hinges on the data you collect from consumers and what your business does with that data, you’ll need to get a complete picture of the personal data you’re collecting, processing, or otherwise interacting with. Follow these items to scope out your data practices:
Identify and document every system (i.e. database, application, or vendor) that 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, including:
Racial or ethnic origins
Religious or philosophical beliefs
Genetic data
Health, sex life, or sexual orientation data
Political opinions
Trade union membership
Biometric data that could uniquely identify someone
Determine whether your documentation meets the GDPR requirements for Records of Processing Activities, that include information on:
The name and contact details of the controller
The purpose behind the processing of data
A description of the categories of data that will be processed
Who will receive the data
Documentation of suitable safeguards for data transfers to a third country or an international organization
The retention period of the different categories of data
A general description of the technical and organizational security measures
Determine whether your documentation includes the following information about processing activities carried out by vendors on your behalf:
The name and contact details of the processor(s) and of each controller on behalf of which the processor is acting, and, where applicable, of the controller’s or the processor’s representative, and the data protection officer
The categories of processing carried out on behalf of each controller
Documentation of suitable safeguards for data transfers to a third country or an international organization
A general description of the technical and organizational security measures
Determine your legal grounds for processing data
GDPR establishes conditions that must be met before you can legally collect or process personal data. Make sure your organization is meeting the conditions listed below:
For each category of data and system/application, determine the lawful basis for processing based on one of the following conditions:
Consent of the data subject
Contract with the data subject
Necessary for compliance with a legal obligation
Necessary in order to protect the vital interests of the data subject or a third party
Necessary for the performance of a task in the public interest or in the exercise of official authority vested in the controller
Necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the rights of the data subject
Review and update current customer and vendor contracts
For your organization to be fully GDPR compliant, the vendors you use must also maintain the privacy rights of your users’ and those rights should be reflected in your contracts with customers:
Review all customer and in-scope vendor contracts to determine that they have appropriate contract language (i.e. Data Protection Addendums with Standard Contractual Clauses).
Determine if you need a Data Protection Impact Assessment
A Data Protection Impact Assessment (DPIA) is an assessment to determine what risks may arise from your data processing and steps to take to minimize them. Not all organizations need a DPIA, the following items will help you determine if you do:
Identify if your data processing is likely to create high risk to the rights and freedoms of natural persons. Considering if your processing involves any of the following:
Automated processing, including profiling, and on which decisions are based that produce legal effects
Special categories of data or data related to criminal convictions and offenses
Monitor any publicly accessible area on a large scale
If any of the above are true, you may need to conduct a data protection impact assessment for existing and new data projects.
Clearly communicate privacy and marketing consent practices
A fundamental element of GDPR compliance is informing consumers of their data privacy rights and requesting consent to collect or process their data. Ensure your website features the following:
A public-facing privacy policy which covers the use of all your products, services, and websites.
Notice to the data subject that include the essential details listed in GDPR Article 13.
Have a clear process for persons to change or withdraw consent.
Update internal privacy policies
Ensure that you have privacy policies that are up to the standards of GDPR:
Update internal privacy notices for EU employees.
Have an employee privacy policy that governs the collection and use of EU and UK employee data.
Determine if you need a data protection officer (DPO) based on one of the following conditions:
The data processing is carried out by a public authority
The core activities of the controller or processor require regular and systematic monitoring of data subjects on a large scale
Review compliance measures for external data transfers
Under GDPR, you’re responsible for protecting the data that you collect and if that data is transferred. Make your transfer process compliant by following these steps:
If you transfer, store, or process data outside the EU or UK, identify your legal basis for the data transfer. This is most likely covered by the standard contractual clauses.
Perform and document a transfer impact assessment (TIA).
Confirm you comply with additional data subject rights
Ensure you’re complying with the following data subject rights by considering the following questions:
Do you have a process for timely responding to requests for information, modifications, or deletion of PII?
Can you 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 an EU-based representative
Depending on how and where your organization is based, you may need a representative for your organization within the European Union. Take these steps to determine if this is necessary:
Determine whether an EU representative is needed. You may not need an EU-rep if the following conditions apply to your organization:
Data processing is occasional
Data processing is not done on a large scale
Data processing doesn’t include special categories or data related to criminal convictions and offenses
Doesn’t risk to the rights and freedoms of data subjects
A public authority or body
If the above conditions do not apply to you, appoint an EU-based representative.
Identify a lead data protection authority (DPA) if needed
GDPR compliance is supervised by the government of whatever EU member-state you’re operating in. If you’re operating in multiple member-states, you may need to determine who your lead data protection authority is:
Determine if you operate in more than one EU state.
If so, designate the supervisory authority of the main establishment to act as your DPA.
Implement employee training
Every employee in your organization provides a window for hackers to gain access to your systems and data. This is why it's important to train your employees on how to prevent security breaches and maintain data privacy:
Provide appropriate security awareness and privacy training to your staff.
Integrate data breach response requirements
GDPR requires you to create a plan for notifying users and minimizing the impact of a data breach. Examine your data breach response plan, by doing the following:
Create and implement an incident response plan which includes procedures for reporting a breach to EU and UK data subjects as well as appropriate data authorities.
Establish breach reporting policies that comply with all prescribed timelines and include all recipients (i.e. authorities, controllers, and data subjects).
Implement appropriate security measures
GDPR requires you to take measures to minimize the risk of a data breach. This includes security practices such as pseudonymization/encryption, maintaining confidentiality, restoration of access following physical/technical incidents, and regular testing of measures. Consider the following:
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 measures ensure that, by default, only personal data that are necessary for each specific purpose of the processing are processed?
Streamline GDPR compliance with automation
GDPR compliance is an ongoing project that requires consistent upkeep with your system, vendors, and other factors that could break your compliance. Automation can help you stay on top of your ongoing GDPR compliance. The following items can help you streamline and organize your continuous compliance:
Explore tools for automating security and compliance.
Transform manual data collection and observation processes via continuous monitoring.
Download this checklist for easy reference
GDPR compliance FAQs
In this section, we’ve answered some of the most common questions about GDPR compliance:
What are the seven GDPR requirements?
The requirements for GDPR compliance are based on a set of seven key principles:
- Lawfulness, fairness, and transparency
- Purpose limitation
- Data minimization
- Accuracy
- Storage limitations
- Integrity and confidentiality
- Accountability
These are the seven requirements you must uphold to be GDPR compliant.
Is GDPR compliance required in the US?
GDPR compliance is mandatory for some US companies. GDPR compliance is not based on where your organization is located but whose data you collect, store, or process. Regardless of where your organization is based, you must comply with GDPR if you are collecting or processing data from EU residents.
What are the four key components of GDPR?
The four components of GDPR include:
- Data protection principles
- Rights of data subjects
- Legal bases for data processing
- Responsibilities and obligations of data controllers and processors
Safeguard your business with GDPR compliance
If your organization collects data from EU residents, GDPR compliance is mandatory for you. It’s important to follow the steps listed above to protect your business from heavy fines and to respect the data privacy rights of consumers.
Vanta provides compliance automation tools and continuous monitoring capabilities that can help you get and stay GDPR compliant. Learn more about getting GDPR compliance with Vanta.
Pre-work for your SOC 2 compliance
Choose the right type of SOC 2 report:
A SOC 2 Type 1 report assesses how your organization aligns with the security controls and policies outlined in SOC 2
A SOC 2 Type 2 report has all the components of a Type 1 report with the addition of testing your controls over a period of time
The correct report will depend on the requirements or requests of the client or partner that has requested a SOC 2 report
from you
Determine the framework for your SOC 2 report. Of the five Trust Service Criteria in SOC 2, every organization needs to comply with the first criteria (security), but you only need to assess and document the other criteria that apply. Determining your framework involves deciding which Trust Service Criteria and controls are applicable to your business using our Trust Service Criteria Guide.
Estimate the resources you expect to need. This will vary depending on how closely you already align with SOC 2 security controls, but it can include several costs such as:
Compliance software
Engineers and potentially consultants
Security tools, such as access control systems
Administrative resources to draft security policies
Auditing for your compliance certification
Obtain buy in from your organization leadership to provide the resources your SOC 2 compliance will need.
Work toward SOC 2 compliance
Begin with an initial assessment of your system using compliance automation software to determine which necessary controls and practices you have already implemented and which you still need to put in place.
Review your Vanta report to determine any controls and protocols within the “Security” Trust Service Criteria that you do not yet meet and implement these one by one. These are multi-tiered controls across several categories of security, including:
CC1: Control Environment
CC2: Communication and Information
CC3: Risk Assessment
CC4: Monitoring Activities
CC5: Control Activities
CC6: Logical and Physical Access Controls
CC7: System Operations
CC8: Change Management
CC9: Risk Mitigation
Using Vanta’s initial assessment report as a to-do list, address each of the applicable controls in the other Trust Services Criteria that you identified in your initial framework, but that you have not yet implemented.
Using Vanta’s initial assessment report, draft security policies and protocols that adhere to the standards outlined in SOC 2.
Vanta’s tool includes thorough and user-friendly templates to make this simpler and save time for your team.
Run Vanta’s automated compliance software again to determine if you have met all the necessary criteria and controls for your SOC 2 report and to document your compliance with these controls.
Complete a SOC 2 report audit
Select and hire an auditor affiliated with the American Institute of Certified Public Accountants (AICPA), the organization that developed and supports SOC 2.
Complete a readiness assessment with this auditor to determine if you have met the minimum standards to undergo a full audit.
If your readiness assessment indicates that there are SOC 2 controls you need to address before your audit, complete these requirements. However, if you have automated compliance software to guide your preparations and your SOC 2 compliance, this is unlikely.
Undergo a full audit with your SOC 2 report auditor. This may involve weeks or longer of working with your auditor to provide the documentation they need. Vanta simplifies your audit, however, by compiling your compliance evidence and documentation into one platform your auditor can access directly.
When you pass your audit, the auditor will present you with your SOC 2 report to document and verify your compliance.
Maintain your SOC 2 compliance annually
Establish a system or protocol to regularly monitor your SOC 2 compliance and identify any breaches of your compliance, as this can happen with system updates and changes.
Promptly address any gaps in your compliance that arise, rather than waiting until your next audit.
Undergo a SOC 2 re-certification audit each year with your chosen SOC 2 auditor to renew your certification.
Download this checklist for easy reference
Prioritizing Your Security and Opening Doors with SOC 2 Compliance
Information security is a vital priority for any business today from an ethical standpoint and from a business standpoint. Not only could a data breach jeopardize your revenue but many of your future clients and partners may require a SOC 2 report before they consider your organization. Achieving and maintaining your SOC 2 compliance can open countless doors, and you can simplify the process with the help of the checklist above and Vanta s compliance automation software. Request a demo today to learn more about how we can help you protect and grow your organization.
Pre-work for your ISO 42001 compliance
Understand ISO 42001 requirements
Decide on what is the scope of the AIMS
Familiarize yourself with key AI concepts, principles, and lifecycle based on ISO frameworks
Determine if you are a provider, developer, or user of AI systems
Perform initial gap analysis
Using Vanta, asses your in-scope ISO 42001 controls
Identify areas of requirement, development, or adjustment
Secure top management support
Present a business case highlighting the benefits of ISO 42001 certification
Define roles and responsibilities for top management in AIMS implementation
Involve various department heads in the analysis to ensure comprehensive coverage
Work for your ISO 42001 compliance
Appoint a Project Manager
Designate an owner for the ISO 42001 implementation project
Develop a project plan
Outline steps, timelines, and resources needed for AIMS implementation
Integrate the AIMS implementation project within existing organizational processes
Establish the AIMS framework
Define the scope and objectives of the AIMS within the organization
Develop and document AI policies and risk management processes
Based on gap analysis, implement necessary controls for AIMS
Ensure integration of AIMS with other management systems and requirements
Create an AIMS statement of applicability (SOA)
Promote competence and awareness
Conduct training for stakeholders on AI concepts and ISO 42001 requirements
Raise awareness about the importance and benefits of AIMS
Implement AIMS controls
Create an AI policy
Define the process for reporting concerns about AI systems
Identify, document, and manage resources for AI systems
Ensure tooling and computing resources for AI systems are adequately documented
Conduct an AI system impact assessment exercise
Ensure that objectives are documented for the design and development of AI systems
Create a process for responsible design and development of AI systems
Ensure that AI system deployment, operation, and monitoring are documented and executed according to your AIMS
Define and implement data management processes for AI systems
Assess and document the quality of data for AI systems
Ensure that system documentation and information for users is provided and accessible
Document and follow the processes for the responsible use of AI systems
Clearly allocate and document responsibilities with third parties
Conduct internal audits
Regularly assess compliance with ISO 42001 and the effectiveness of AIMS
Management review
Review AIMS performance and compliance with top management
Address any non conformities and areas for improvement
Prepare for your external audit
Work with A-LIGN as your ISO 42001 certification body
Engage A-LIGN, a leading ISO certification body, to conduct your audit
Prepare documentation
Ensure all AIMS documentation is up to date and accessible
Pre-audit meeting
Prepare a list of questions and clarifications regarding the audit process
Initial sales process
Discuss the scope of the audit in detail to ensure full preparedness
Conduct a pre-certification audit (optional)
Consider a pre-certification audit to identify any remaining gaps
The ISO 42001 audit
Engage in the certification audit
Collaborate with A-LIGN auditors, providing necessary information and access
Designate a team member as the point of contact for auditors to streamline communication
Organize walkthroughs to discuss your AIMS processes and procedures, including facilities (if applicable)
Address audit findings
Plan for immediate, short-term, and long-term corrective actions based on the audit report
Celebrate the audit success with your team and publicly promote your certification
Continuous improvement
Establish a continuous improvement team to oversee progress post-certification
Continuously improve the AIMS, leveraging lessons learned and feedback
Integrate ISO 42001 compliance metrics into regular management reviews
Keys to success
Leverage Vanta s readiness capabilities and A-LIGN s expertise for an efficient and high-quality audit experience from
readiness to report
Incorporate AIMS within the business strategy and daily operations
Apply continuous improvement to enhance AIMS over time
Avoid integrating new technologies during the initial AIMS implementation
Engage interested parties and maintain their support throughout
Highlight the completion of the audit to demonstrate trust with customers, partners, and other key stakeholders
Download this checklist for easy reference
Demonstrating secure AI practices with ISO 42001
The rapid adoption of AI has driven innovation and opportunities for growth — and with it, new risks for the companies that manage the data that power these technologies. These companies have not had a way to demonstrate trust to their customers and show that they are deploying AI securely and safely. Achieving ISO 42001 compliance helps to demonstrate this trust through a third-party verifiable way and opens the doors to time-savings, more deals, and expedited sales processes. The above checklist simplifies the process of becoming ISO 42001 compliant by leveraging the power of Vanta's continuous compliance software. Request a demo today to learn more about how Vanta can help you streamline the path to ISO 42001.
Develop a roadmap for your ISMS implementation and ISO 27001 certification
Implement Plan, Do, Check, Act (PDCA) process to recognize challenges and identify gaps for remediation
Consider the costs of ISO 27001 certification relative to your organization’s size and number of employees.
Use project planning tools like project management software, Gantt charts, or Kanban boards.
Define the scope of work from planning to completion.
Determine the scope of your organization’s ISMS
Decide which business areas are covered by your ISMS and which ones are out of scope
Consider additional security controls for processes that are required to pass ISMS-protected information across the trust boundary.
Communicate the scope of your ISMS to stakeholders.
Establish an ISMS team and assign roles
Select engineers and technical staff with experience in information security to construct and implement the security controls needed for ISO 27001.
Build a governance team with management oversight.
Incorporate key members of top management (senior leadership and executive management) and assign responsibility for strategy and resource allocation.
If you have a large team, consider assigning a dedicated project manager to track progress and expedite implementation.
Align the team on the following:
The planning steps you’ve already taken
The scope of the ISMS
Which team members are responsible for which aspects of the project
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
Meet with your team to discuss this inventory and ensure that everyone is aligned.
Perform 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 that you identified during your risk assessment.
Summarize each identified risk
Indicate the impact and likelihood of each risk.
Rank risk scenarios based on overall risk to the organization’s objectives.
Document a risk treatment plan
Design a response for each risk, known as a risk treatment.
Assign an owner to each identified risk and each risk mitigation activity.
Establish target timelines for completion of risk treatment activities.
Implement your risk mitigation treatment plan and track the progress of each task.
Complete the Statement of Applicability
Review the 93 controls listed in Annex A.
Select the controls that are relevant to the risks you identified in your risk assessment.
Complete the Statement of Applicability listing all Annex A controls, justifying inclusion or exclusion of each control in your ISMS implementation.
Implement ISMS policies, controls and continuously assess risk
Assign owners to each of the security controls to be implemented.
Figure out a way to track the progress and goals for each control.
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
- Communication
- Internal Audit
- Management Review
- Corrective Action and Continual Improvement
- Policy Violations
- All of the Annex A controls that you have selected
Establish employee training and awareness programs
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.
Make security training part of the onboarding process for new employees.
Conduct regular training to ensure awareness of new policies and procedures.
Conduct regular management reviews
Plan reviews at least once per year. Consider a quarterly review cycle if your organization is large or if your infrastructure is changing frequently.
Ensure the ISMS and its objectives continue to be effective.
Verify that senior management stays informed.
Ensure risks or deficiencies can be promptly addressed.
Assemble ISO 27001 required documents
Review the ISO 27001 Required Documents and Records list.
Customize policy templates with organization-specific policies, process, and language.
Perform an ISO 27001 internal audit.
Examine each of the requirements from Annex A that you deemed applicable in your ISMS' Statement of Applicability and verify that you have each in place.
Assign in-house employees to conduct the internal audit, specifically employees who were not involved in the ISMS development and maintenance or hire an independent third party.
Share internal audit results, including nonconformities, with the ISMS team and senior management.
Address any issues your internal audit identified before proceeding with the external audit.
Verify compliance with the requirements from Annex A deemed applicable in your ISMS' Statement of Applicability.
Undergo external audit of ISMS to obtain ISO 27001 certification.
Select an independent ISO 27001 auditor.
Complete the Stage 1 Audit consisting of an extensive documentation review; obtain the auditor’s feedback regarding your readiness to move to the Stage 2 Audit.
Complete the 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 addressed.
Ensure your organization is following the processes that it has specified and documented.
Ensure your organization 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.
Plan for subsequent ISO 27001 audits and surveillance audits.
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
Learn more about achieving ISO 27001 certification with Vanta
Book an ISO 27001 demo with Vanta
Download this checklist for easy reference
Prioritizing your security and opening doors with ISO 27001 compliance
Information security is a vital priority for any business today from an ethical standpoint and from a business standpoint. Not only could a data breach jeopardize your revenue, but many of your future clients and partners may require an ISO 27001 report before they consider your organization. Achieving and maintaining your ISO 27001 compliance can open countless doors, and you can simplify the process with the help of the checklist above and Vanta’s compliance automation software.
Request a demo today to learn more about how we can help you protect and grow your organization.
Develop a roadmap for your ISMS implementation and ISO 27001 certification
Implement Plan, Do, Check, Act (PDCA) process to recognize challenges and identify gaps for remediation
Consider the costs of ISO 27001 certification relative to your organization’s size and number of employees.
Use project planning tools like project management software, Gantt charts, or Kanban boards.
Define the scope of work from planning to completion.
Determine the scope of your organization’s ISMS
Decide which business areas are covered by your ISMS and which ones are out of scope
Consider additional security controls for processes that are required to pass ISMS-protected information across the trust boundary.
Communicate the scope of your ISMS to stakeholders.
Establish an ISMS team and assign roles
Select engineers and technical staff with experience in information security to construct and implement the security controls needed for ISO 27001.
Build a governance team with management oversight.
Incorporate key members of top management (senior leadership and executive management) and assign responsibility for strategy and resource allocation.
If you have a large team, consider assigning a dedicated project manager to track progress and expedite implementation.
Align the team on the following:
The planning steps you’ve already taken
The scope of the ISMS
Which team members are responsible for which aspects of the project
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
Meet with your team to discuss this inventory and ensure that everyone is aligned.
Perform 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 that you identified during your risk assessment.
Summarize each identified risk
Indicate the impact and likelihood of each risk.
Rank risk scenarios based on overall risk to the organization’s objectives.
Document a risk treatment plan
Design a response for each risk, known as a risk treatment.
Assign an owner to each identified risk and each risk mitigation activity.
Establish target timelines for completion of risk treatment activities.
Implement your risk mitigation treatment plan and track the progress of each task.
Complete the Statement of Applicability
Review the 93 controls listed in Annex A.
Select the controls that are relevant to the risks you identified in your risk assessment.
Complete the Statement of Applicability listing all Annex A controls, justifying inclusion or exclusion of each control in your ISMS implementation.
Implement ISMS policies, controls and continuously assess risk
Assign owners to each of the security controls to be implemented.
Figure out a way to track the progress and goals for each control.
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
- Communication
- Internal Audit
- Management Review
- Corrective Action and Continual Improvement
- Policy Violations
- All of the Annex A controls that you have selected
Establish employee training and awareness programs
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.
Make security training part of the onboarding process for new employees.
Conduct regular training to ensure awareness of new policies and procedures.
Conduct regular management reviews
Plan reviews at least once per year. Consider a quarterly review cycle if your organization is large or if your infrastructure is changing frequently.
Ensure the ISMS and its objectives continue to be effective.
Verify that senior management stays informed.
Ensure risks or deficiencies can be promptly addressed.
Assemble ISO 27001 required documents
Review the ISO 27001 Required Documents and Records list.
Customize policy templates with organization-specific policies, process, and language.
Perform an ISO 27001 internal audit.
Examine each of the requirements from Annex A that you deemed applicable in your ISMS' Statement of Applicability and verify that you have each in place.
Assign in-house employees to conduct the internal audit, specifically employees who were not involved in the ISMS development and maintenance or hire an independent third party.
Share internal audit results, including nonconformities, with the ISMS team and senior management.
Address any issues your internal audit identified before proceeding with the external audit.
Verify compliance with the requirements from Annex A deemed applicable in your ISMS' Statement of Applicability.
Undergo external audit of ISMS to obtain ISO 27001 certification.
Select an independent ISO 27001 auditor.
Complete the Stage 1 Audit consisting of an extensive documentation review; obtain the auditor’s feedback regarding your readiness to move to the Stage 2 Audit.
Complete the 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 addressed.
Ensure your organization is following the processes that it has specified and documented.
Ensure your organization 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.
Plan for subsequent ISO 27001 audits and surveillance audits.
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
Learn more about achieving ISO 27001 certification with Vanta
Book an ISO 27001 demo with Vanta
Download this checklist for easy reference
Download NowPlan strategically when scheduling and timing your audit
Sometimes, the biggest roadblock to scheduling an audit is knowing where to start. Here are a few tips for taking your first big step in the audit process.
Check into your chosen firm’s availability. Small auditing firms tend to have more limited time and need more advance notice, while larger firms have more resources and, therefore, more availability. However, larger firms can cost more to hire.
Give yourself enough time before the audit. In many cases, audits don’t just check to see if you’ve done an activity once; they look for evidence of continuous controls. Plan to collect consistent evidence over at least three months to demonstrate this.
Choose a dedicated team or team member who will be available throughout the audit. Your auditor will need a go-to person to provide all the proper information and be available for any follow-up questions. Check calendars of others stakeholders involved with the audit controls to ensure they’ll be present when you schedule your audit on-site or live sessions.
Be aware of commitments and deadlines. You will likely sign a statement of work (SOW) when you schedule an audit. Your team is responsible for meeting all the deadlines outlined in this SOW. The auditor will need the correct information from your team in a timely manner to do their job.
Pro tip: Make sure your team understands the difference between the “audit window” or “review period” and the length of the audit itself. The “audit window” is the timeframe the auditors will use to gauge if you’ve been consistent with your controls. Typically, they require three months or more. This time period is different from the 1-4 weeks that the auditor will be inside your organization, conducting the audit itself.
Prepare your team in advance
Once you’ve scheduled your audit, it’s time to work with your team and assign tasks to the appropriate owners. An audit requires participation from several teams, from engineering to IT to sales. Here are a few ways to prepare these teams for audit-related activities:
Know which framework(s) you’re working towards and communicate the requirements to your team. If you’re going to work towards multiple frameworks simultaneously, identify overlaps so you don’t duplicate work. A tool like Vanta helps break down requirements and map them to action items.
Understand which evidence each team needs to provide. Next, communicate requirements and deadlines to each department. It’s a good idea to use a central hub that can show all preparation activities and who is responsible for each one.
Inform your team why this is an important activity so they understand that the time and commitment are worthwhile for them. Connect it to outcomes and KPIs that matter to their teams whenever possible. Audits ultimately prove your company’s commitment to security and trust, and meeting a framework can be the difference between growing your business and missing out on opportunities.
Communicate to your team that the goal is progress, not perfection. If it’s your first time getting audited against a particular framework, you probably won’t get a perfect score, and that’s okay! Instead, make it your goal to set a baseline for meeting the framework, then find ways to improve your controls over time.
Pro tip: As you and your team prepare for the audit, remember to do your due diligence before the auditor even arrives. Get to know exactly how your controls align with the framework and be realistic about which shortcomings you expect the auditor will likely find. That way, you won’t be surprised by the audit’s findings.
Manage your evidence
As your team prepares for an audit, collecting evidence of your activities is just as important as completing the activities themselves. For example, you will likely need to draft formal security policies and protocols (for example, this is one of the requirements for SOC 2). But you can’t just say, “We have the required security policies.” You’ll need to provide your auditor with a hard copy of your policies. And this is just one of the many controls they will require you to prove with documentation.
Managing evidence gets complicated quickly, considering how many documents your auditor will require. So, it’s your job to make sure that evidence is organized and ready as soon as the auditor asks for it. Here are a few tips for compiling the proper evidence to be fully prepared when the auditor arrives:
Ensure your evidence shows consistency —not just point-in-time or static documentation. You should be able to prove that you’ve maintained the proper controls throughout your audit window. A tool like Vanta that supports continuous controls monitoring can help with this.
Compile and store your documentation in a way that simplifies sharing the relevant evidence with the auditor. You want to spend as little time as possible chasing down specific documents or screenshots during the audit. Getting organized beforehand means far less stress for your team when the auditor begins their assessment. Vanta can help you stay on top of your documentation by storing all documents in a centralized location and automatically updating data with real-time changes.
Get to know your evidence inside and out. You shouldn’t be surprised by anything that your auditor finds. It helps to use a governance, risk, and compliance (GRC) automation tool to parse through the documentation and summarize findings. This way, you have a consolidated view of evidence rather than a bunch of disparate documents and files that are hard to consume at once.
Be transparent and upfront with your evidence. Don’t try to shape a specific story or alter the truth by showing more or less documents to an auditor. Honesty is always the best policy in these cases, especially considering the potential consequences of lying in an audit. Altering the truth can significantly impact the integrity of your company, or even prevent you from requesting audits in the future.
Pro tip: Be transparent without embellishing the truth when the auditor arrives. Let your evidence speak for itself. You might think this goes without saying, but the temptation to overshare or embellish can get the best of anyone when the audit actually begins.
Work closely with your auditor
Many organizations enter the auditing process with concerns about their relationship with the auditor. Fortunately, in most cases, the process will be less like a test proctored by an intimidating professor and more of a back-and-forth conversation with an industry expert who knows best how to get you to your goals.
Here’s some advice for working with your auditor and making it a better experience for both of you:
Look for specialization. Find an auditor specializing in the framework(s) you’re working toward. You can start by asking for recommendations within your industry—Vanta’s network of trusted auditors is a great place to start.
Help your auditor understand your business. You will need to guide them through the ins and outs of your organization, including where your controls reside and which insights they provide to your business. They won't know where to start assessing your controls if they don’t understand your organization or GRC processes and tools.
Treat the audit like a conversation. In most cases, your auditor will be inside your organization for a few weeks to months, and during that time, it should become a back-and-forth working relationship. The auditor will likely ask you for specific evidence over time, and you will work with them directly to provide each piece of information they need, and so on.
Maintain the relationship with your auditor afterward. They can serve as a helpful resource as you build out your GRC initiatives and continuously maintain and improve compliance over time. While auditors can’t give direct advice on how to do something, most are more than willing to help wherever they can. For example, if you plan to change your tech stack, employee policies, etc., consider asking your auditor how these changes will impact future audits before committing to the change.
Pro tip: Keep in mind that it’s common practice to switch your auditor every few years to avoid bias. But once you’ve found a firm and auditor you like, you can always ask them for recommendations and referrals to find your next auditor.
Take your audit results to the next level
An audit isn’t just a one-and-done activity—it’s the beginning of a journey toward a stronger security posture over time. To get the most out of your audit findings, prepare your team to work on the following initiatives after the audit is done:
Share your new compliance status with the right audiences. Many businesses rely use a public-facing site (like Vanta Trust Center) to display their real-time GRC efforts. Your prospective customers can then use this data to expedite security questionnaires and provide proof points to key decision-makers.
Track KPIs that show your response to the gaps that your auditor finds. The specifics of these KPIs will depend on your particular business, priorities, etc. In general, they should center around risk reduction and remediation efforts. For instance, if you have any findings, opportunities for improvement (OFI), or nonconformities listed in your report, track the response to these insights over time. How are you changing processes? What new tools have you implemented?
Consider conducting a readiness assessment between formal external audits. Businesses will typically either hire a third party or pick a team member who isn’t involved in any GRC activities to perform this type of audit. The best way to incorporate readiness assessments into your processes without causing business disruption is to use continuous monitoring to get an instant snapshot of all existing controls.
Treat your audit like a jumping-off point for security initiatives. Meeting a particular framework doesn’t necessarily equate to bulletproof security. For example, a compliance framework often doesn’t account for emerging threats. Still, consistently meeting the controls listed in a framework is a great starting point for establishing a strong security culture throughout your organization.
Foster a strong security culture. As you respond to your audit findings and implement stronger GRC controls, your team members need to understand why specific controls exist and how to play a role in meeting them. Ultimately, this is all about fostering a strong security and risk management culture throughout your organization. Consider rolling out security training and tracking KPIs such as phishing drill click-through rates and training completion rates. This will help demonstrate progress for future audits as well as improving your organization’s security posture.
Pro tip: Keep in mind that it’s common practice to switch your auditor every few years to avoid bias. But once you’ve found a firm and auditor you like, you can always ask them for recommendations and referrals to find your next auditor.
Anatomy of an audit report
Knowing what to expect when you finally get that audit report can help you set expectations for internal and external stakeholders ahead of time. Here’s what the typical audit report should contain:
- Executive summary: A high-level recap of the report’s purpose, the standard/framework in question, etc.
- Scope: An in-depth description of the scope that the audit covered. For example, was it a corporate-wide evaluation, a test on a specific application, or something else?
- Testing information: A detailed list of all tests the auditor ran, such as policy reviews, artifact evaluations, and on-site observations.
- Testing results: A report on the results of these tests, including any exceptions.
- Management responses: The management team’s explanations as to why an exception exists and how they will respond to it in the future.
- Conclusion: The auditor’s opinion on the assessment. Keep in mind that this area of the report will rank the company by maturity, not as a pass or fail.
While compliance audits can feel overwhelming because of the time and resources that they require, they offer your team the unique opportunity to start a journey toward stronger security and deeper customer trust. Plus, tasks like scheduling, managing evidence, and working with your auditor don’t have to feel so daunting if you go into your next audit with the right expectations and preparation.
Pre-work for your Cyber Essentials certification
Evaluate your need for Cyber Essentials. You can assess whether you need a Cyber Essentials certification based on the following criteria:
Do you collect or process sensitive or personal data from UK residents?
Have you ever been asked about Cyber Essentials by clients or prospects?
Do your competitors have Cyber Essentials certification?
Are you working with companies that provide public services in the UK?
Choose the right Cyber Essentials certification. Although both versions of the Cyber Essentials frameworks have the same requirements, Cyber Essentials Plus involves a third-party audit and technical testing. As a result, Cyber Essentials Plus provides an extra layer of security validation beyond the self-assessment in the standard Cyber Essentials certification.
Do you need Cyber Essentials or Cyber Essentials Plus?
Here are some helpful considerations for deciding whether to pursue the Cyber Essentials certification or Cyber Essentials Plus:
Determine your budget. Cyber Essentials Plus is more expensive than Cyber Essentials because of the external audit and higher security assurance. Pricing for Cyber Essentials ranges from £320 to £600 (plus VAT). Cyber Essentials Plus does not have a fixed pricing structure, but estimates start at £1,499 (plus VAT) and increase based on your organisation’s size and complexity. Learn more about Cyber Essentials costs.
Assess your time and team resources. Cyber Essentials Plus requires more time and bandwidth and takes longer to complete, especially for smaller companies (or security teams) with limited internal resources.
Understand your stakeholders’ concerns. The Cyber Essentials Plus third-party audit requirement enables you to demonstrate your commitment to enterprise-wide data security and assure stakeholders who may have security concerns.
Define customer requirements. Cyber Essentials Plus is required to win UK government contracts. It may also be required to conduct business with certain companies in the UK, such as those looking to prevent potential supply chain-related cyber threats from impacting their operations.
Evaluate your infrastructure size and complexity. Larger, more complex entities whose interconnected assets and operations are at high risk of being disrupted by cyber threats may benefit from Cyber Essentials Plus. Its rigour ensures reliable safeguards protect this infrastructure.
Estimate the volume and sensitivity of stored data. Companies that handle vast amounts of sensitive data (such as PHI in healthcare) may gain higher assurance with Cyber Essentials Plus.
Prepare for your Cyber Essentials certification
First, identify your Cyber Essentials requirements.
Obtaining a Cyber Essentials certification requires you to implement controls across five categories:
Firewalls: All firewalls deployed to system boundaries, endpoints, servers, cloud services, and other critical infrastructure entry points should have the correct security configurations, access controls, and security rules.
Secure configurations: All configurations applied to endpoints and networked services should reduce exploitable vulnerabilities while enabling the completion of business-critical services.
User access controls: Access to all user accounts should require authorisation, and only the people who need access to specific endpoints, services, or applications to complete business tasks should have access. Consider using time-bound or just-in-time access and implementing the principle of least privilege (PoLP) to tighten user access controls.
Malware protection: Administrators should establish the appropriate security mechanisms to prevent malware intrusion via known and unknown sources. They should also educate employees and third parties on the risks of malware and ransomware and how to avoid social engineering scams.
Security updates: All devices and software at risk for security flaws should be updated regularly to ensure their configurations are secure and in alignment with recommended industry/manufacturer security standards.
Gap analysis and remediation
Conduct a gap analysis. Evaluate IT infrastructure for gaps in the above control categories.
Document gaps and develop a remediation plan. Documenting the gaps identified and proposing actionable steps to rectify them is critical.
Address gaps that could lead to security vulnerabilities. Following a gap analysis, you may need to remediate sources of exploitable vulnerabilities.
Examples of remediation steps include:
Changing default administrative passwords into stronger, unique ones
Deactivating unnecessary user accounts that are not currently in use
Scheduling automatic system and network security updates
Implementing multi-factor authentication for all user accounts
Installing anti-malware software on all devices
Test all applicable controls. It’s critical to monitor devices and networks to verify the effectiveness of implemented controls in preparation for assessment. Test your controls and make sure they are functioning properly.
Document findings from system monitoring. It’s also helpful to record all the information from monitoring in an organised, shareable report format to keep track of it. Doing so manually is a challenge for any organisation, which is where automation solutions, like Vanta, help reduce these burdens and enable organisations to scale their security monitoring capabilities as they grow.
Complete the self-assessment (for Cyber Essentials)
After you’ve identified the Cyber Essentials requirements that apply to your organisation and remediated any security gaps, the next step towards becoming Cyber Essentials certified is to complete the self-assessment, which is required even when you’re aiming for the Cyber Essentials Plus certification. Here are the steps our team of compliance experts recommend taking:
Prepare for the Cyber Essentials self-assessment. Train all parties involved in the certification process so they are on the same page regarding Cyber Essentials documentation. Building and maintaining a security awareness culture is crucial for your organisation to fully comply with Cyber Essential security guidelines during its day-to-day operations beyond preparing for the Cyber Essentials self-assessment (or audit, if you choose to pursue Cyber Essentials Plus).
Conduct the self-assessment questionnaire. (SAQ). When ready, you can complete an online SAQ and have a senior team member validate it to get the Cyber Essentials certificate. It’s essential to be accurate and truthful when answering questions to ensure alignment with the necessary standards for obtaining the certificate.
Use online readiness tools to prepare for the test. Tools like the IASME Cyber Essentials Readiness Tool provide free questions to help you assess the posture of your company’s controls and their impact on your business operations. These questions are designed to inform you about your current readiness so you can develop a tailored action plan for the Cyber Essentials audit.
Decide whether you need the Cyber Essentials Plus audit. You can choose to obtain the Cyber Essentials Plus certification immediately after the Cyber Essentials self-assessment or in the following months. While you must complete just the self-assessment to obtain the Cyber Essentials certification, you’ll also need to complete and pass an external audit to receive the Cyber Essentials Plus certification.
Complete the external audit for Cyber Essentials Plus
Prepare for the Cyber Essentials Plus audit. If you want to obtain a Cyber Essentials Plus certification, you should ensure your SAQ was certified within three months of applying for the Cyber Essentials Plus.
Identify an independent assessor: Work with a highly-trained assessor to verify that all currently implemented controls align with the Cyber Essentials Plus requirements.
Review audit findings and implement remedial actions (if any): Address any gaps identified during the independent assessment within a set period.
Obtain Cyber Essentials Plus certification: A successful Cyber Essentials Plus certification provides a certificate valid for 12 months following the assessment pass date. Then, you can become designated as a CE-certified company, opening new business opportunities in the private sector or with the UK government.
Maintain ongoing Cyber Essentials or Cyber Essentials Plus certification
Monitor your IT infrastructure regularly. Organisations need continuous internal assessments to verify adherence to the Cyber Essentials security guidelines. As systems and networks age, they are exposed to more vulnerabilities. So, you need to review your existing security configurations and ensure they still match the rigorous standards of the Cyber Essentials or Cyber Essentials Plus program.
Renew your Cyber Essentials certification.The Cyber Essentials and Cyber Essentials Plus certifications expire after 12 months and must be renewed yearly. Renewing these certifications helps you maintain your designation as a Cyber Essentials-certified company and provides assurance to current and future stakeholders.
Implement zero-trust principles. As the cyber risk environment becomes more complex, consider implementing zero trust across systems and networks to keep your data safe. New technologies are constantly emerging, meaning cybercriminals are also looking for the easiest gaps to exploit to access sensitive data for malicious gain.
Streamline Cyber Essentials certification with Vanta
A strong security posture will enable organisations to build customer trust and expand business to or within the UK. However, it’s cumbersome to manually keep track of all the processes necessary to obtain Cyber Essentials or Cyber Essentials Plus certification.
Fortunately, Vanta automates up to 70% of the UK Cyber Essentials process (including evidence collection), dramatically simplifying the compliance process. This enables teams to focus on strengthening their security programs without redundancy.
Plus, with Vanta, you don’t need to duplicate your compliance efforts across multiple frameworks. UK Cyber Essentials has significant overlap with frameworks like ISO 27001. If you’re already compliant with ISO 27001, you don’t need to reinvent the wheel; Vanta automatically cross-references other frameworks and surfaces any overlapping controls that you already have in place.
Vanta’s trust management expertise can help startups and early-stage companies in the UK build and optimise their security programs to obtain the Cyber Essentials certification. Thousands of global customers rely on Vanta’s real-time, transparent trust management platform to demonstrate their focus on security and privacy to stakeholders.
Learn more about how Vanta automates Cyber Essentials compliance.
Pre-work for your HITRUST certification
Align your goals: Ensure that pursuing a HITRUST certification aligns with your business goals and programs
Find internal stakeholders: Identify key stakeholders within your organization, such as champions who can drive internal buy-in, and a project owner to drive the certification process
Educate leadership: Educate your team, executives, and the board on the HITRUST process, implied changes, and the added value to your organization of attaining certification
Work for your HITRUST certification
Understand the HITRUST CSF: Familiarize yourself with the control requirements of the HITRUST CSF
Identify compliance needs: Determine your organization's specific compliance requirements
Select appropriate HITRUST assessment type: Choose between e1, i1, or r2 assessment, according to needs of your business and your risk profile
Use Vanta to streamline the assessment: Use Vanta to identify and remediate gaps in your compliance program
Find an external assessor: Work with Vanta to select a HITRUST Validated Assessor—A-LIGN, Prescient Assurance, or Insight Assurance—to guide you through and to conduct your Readiness assessment
Purchase MyCSF subscription: Work with Vanta to initiate the procurement process for your Validated Assessor, MyCSF subscription, and report credit (if required)
Attend the HITRUST course: Gain insights and guidance through HITRUST’s New Customer Orientation
Define assessment scope: Identify the areas and systems to be included in the assessment and communicate the intended timeline of certification to your chosen Validated Assessor
Perform initial assessment: Work with your external assessor to identify gaps using Vanta
Initiate inheritance plans: Create plans for internal or external inheritance of controls
Make inheritance requests: Submit inheritance requests via the MyCSF platform
Secure QA date: Schedule a date for post-submission HITRUST QA review
Remediation
Resolve gaps: Use Vanta to identify and remediate any evidence gaps identified during the readiness assessment
The Validated Assessment
Provide evidence: Collect and submit necessary evidence to your external assessor
Finalize inheritance: Confirm all inheritance plans
Support External Assessor: Be available for any additional validation requests
Address issues: Resolve any issues noted during the pre-submission QA
Submission and Review
Submit assessment: Submit the relevant evidence to your chosen Validated Assessor to input into MyCSF for HITRUST to review
Support QA process: Be available to assist your external assessor with any QA queries
Certification
Review certification report: Check and approve the draft certification report
Ensuring compliance over time and beyond
Ongoing Monitoring
Remediate gaps: Use Vanta to continue to monitor your state of compliance and continue to close gaps
Plan for the next assessment
Future planning: Prepare for your next HITRUST assessment to maintain compliance, manage risks, and enhance security —
leveraging inheritance where appropriate
Advancing your assessment: Consider expanding your security posture by exploring the different levels within the HITRUSTecosystem — from e1 to i1 and i1 to r2
Leverage the business benefits of HITRUST certification, including
Commercial compliance: Satisfy customer, contractual requirements or preferences for HITRUST certification
Market access: Gain access to new or additional markets that require or prefer HITRUST certification
Market differentiator: Demonstrate the highest level of security posture as a vendor or partner
Risk mitigation: Adopt proven, repeatable, and measurable methods ensure significant risk reduction in certified environments
(only 0.64% of experienced breaches over two years)
Value creation: Improve potential valuation with investors and shareholders
Liability reduction: Protect yourself and your organization by using a prescriptive, complete, and proven framework to plan,
build, execute, and validate your cybersecurity program instead of building your own
Regulatory compliance: Reuse and restate HITRUST validated controls using HIPAA, SOC 2, ISO 27001, GDRP, and others to reduce compliance efforts
Download this checklist for easy reference
Download NowDetermine 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 reference
Download NowJess Chang
Allan Reyes
FEATURED VANTA RESOURCE
The ultimate guide to scaling your compliance program
Learn how to scale, manage, and optimize alongside your business goals.
.svg)
Security
Vanta events | Vanta
The State of Trust 2024: How UK Businesses are managing risk and compliance with automation
Join our upcoming webinar, where leading cybersecurity experts Ciaran Martin and Victoria Baines will discuss findings from Vanta’s second annual State of Trust Report. Understand the risks facing UK organisations, why good security means good business and how to minimise manual security work through AI and automation.
.svg)
.svg)
