Skip to content

Zero Trust Strategy

5 automated security scanners


Purpose: The Zero Trust Maturity Assessment Scanner evaluates the implementation gaps and architectural flaws in an organization’s zero-trust strategy by probing direct infrastructure components such as DNS, HTTP, TLS, ports, and APIs. This helps identify vulnerabilities that could be exploited to bypass security controls.

What It Detects:

  • Security Headers Analysis: Checks for the presence of critical security headers like Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  • TLS/SSL Configuration Issues: Identifies outdated or insecure TLS versions (e.g., TLSv1.0, TLSv1.1) and detects weak cipher suites such as RC4, DES, and MD5.
  • DNS Record Validation: Validates SPF records for proper configuration and checks DMARC policies to ensure they are set appropriately. It also verifies DKIM records for domain key identification.
  • HTTP Response Analysis: Analyzes redirects and content for potential security issues and examines response headers for missing or misconfigured security directives.
  • Port and Service Fingerprinting: Scans common ports to identify open services and performs service fingerprinting to determine the software running on each port.

Inputs Required:

  • domain (string): Primary domain to analyze (e.g., acme.com)

Business Impact: This scanner is crucial for organizations aiming to implement a robust zero-trust architecture, as it helps in identifying and addressing vulnerabilities that could be exploited by attackers. The findings from this scanner can guide security improvements and compliance efforts, enhancing the overall security posture of an organization’s digital infrastructure.

Risk Levels:

  • Critical: Conditions where outdated or insecure TLS versions are present, especially if they support weak cipher suites.
  • High: Absence of critical security headers in HTTP responses, which can lead to various attacks such as MITM (Man-in-the-Middle) and data theft.
  • Medium: DNS records not properly configured for SPF, DMARC, or DKIM, potentially allowing unauthorized access or identity spoofing.
  • Low: Minor issues with port configurations that do not directly impact security but can be improved for better operational efficiency.
  • Info: Informal findings related to missing or misconfigured headers and TLS settings that are less critical but still need attention for continuous improvement.

Example Findings:

  1. The domain example.com lacks the Strict-Transport-Security header, which could lead to persistent HTTP connections being upgraded to HTTPS automatically by browsers.
  2. DNS records for secure.org indicate outdated SPF and DMARC policies that do not effectively protect against phishing attacks or unauthorized access.

Purpose: The Zero Trust Roadmap Development Scanner is designed to assess and identify prioritization issues and implementation challenges in a company’s zero-trust strategy by evaluating their security documentation, public policy pages, trust center information, and compliance certifications. This tool aims to ensure that the organization is adequately addressing critical security areas and meeting necessary standards.

What It Detects:

  • Security Policy Indicators: The scanner checks for the presence of key security policies such as “security policy,” “incident response,” “data protection,” and “access control.”
  • Maturity Indicators: It identifies compliance certifications and maturity indicators like SOC 2, ISO 27001, penetration testing, and vulnerability scanning.
  • Documentation Accessibility: The scanner evaluates the accessibility of company security documentation on their website to ensure transparency and thoroughness in their zero-trust strategy.
  • Public Policy Pages: It reviews public policy pages for adherence to best practices and inclusion of necessary security measures and compliance standards.
  • Trust Center Information: Analyzes trust center information for detailed disclosures about security controls, incident response procedures, and data protection mechanisms.

Inputs Required:

  • domain (string): Primary domain to analyze (e.g., acme.com)
  • company_name (string): Company name for statement searching (e.g., “Acme Corporation”)

Business Impact: This scanner is crucial as it helps in assessing the effectiveness of a company’s zero-trust strategy, identifying gaps and areas where improvements are needed to enhance overall security posture.

Risk Levels:

  • Critical: The scanner identifies critical conditions such as lack of any identified policy or certification.
  • High: Conditions that indicate significant deficiencies in security practices without immediate critical impact but posing a high risk over time.
  • Medium: Conditions where improvements are recommended to align with best practices and standards, though they do not immediately threaten critical operations.
  • Low: Informal findings indicating minor deviations from ideal practices or areas for continuous improvement.
  • Info: General information about the company’s online presence without immediate security implications but useful for general awareness.

Example Findings:

  • The scanner might flag a public policy page that lacks explicit mention of data protection protocols, posing a medium risk due to potential gaps in compliance with regulatory standards.
  • An absence of any security policies or certifications on the trust center could be flagged as critical, indicating severe deficiencies in basic cybersecurity practices.

Purpose: The Risk-Based Access Definitions Scanner is designed to evaluate the accuracy of risk models and the appropriateness of access levels within an organization by analyzing various components such as security documentation, public policy pages, trust center information, and compliance certifications.

What It Detects:

  • Identifies mentions of “security policy” across company websites to ensure comprehensive coverage.
  • Checks for references to “incident response” procedures that demonstrate preparedness in handling potential threats.
  • Verifies the presence of “data protection” measures safeguarding sensitive information, which is crucial for preventing data breaches and maintaining confidentiality.
  • Ensures robust “access control” mechanisms are in place to manage user permissions effectively.
  • Detects compliance with SOC 2 standards, a widely recognized standard for trust services that assesses how well companies protect customer data.
  • Identifies ISO 27001 certification, an international standard for information security management systems, which signifies high standards in managing and protecting sensitive information.
  • Looks for evidence of “penetration test” activities to assess the vulnerabilities of system infrastructure and improve overall security posture.
  • Checks for practices such as “vulnerability scan” or “assessment,” indicating regular evaluations of potential risks and weaknesses within the organization’s systems.

Inputs Required:

  • domain (string): The primary domain of the company website to be analyzed, which helps in gathering relevant security information from various pages.
  • company_name (string): The name of the company, used for searching specific statements and policies related to the organization’s security measures.

Business Impact: This scanner is crucial as it provides a detailed analysis of an organization’s security documentation and policy adherence, which directly impacts the overall risk profile and compliance posture of the enterprise. Misalignment between stated policies and actual practices can lead to significant vulnerabilities that may be exploited by malicious actors, potentially resulting in severe financial losses, reputational damage, and legal repercussions.

Risk Levels:

  • Critical: Conditions where there are no mentions or explicit references to any security policy or related procedures within the documentation. This could indicate a complete lack of preparedness for potential threats and risks.
  • High: Conditions where specific security measures such as access control, data protection, or incident response are either not mentioned at all in the provided documents or there is a significant gap between stated policies and actual practices.
  • Medium: Conditions where some security aspects like policy completeness or certain compliance certifications are present but do not meet industry standards or best practices.
  • Low: Conditions where minor gaps exist in documentation, such as missing specific references to certain procedures or lacking detailed information on how certain measures are implemented.
  • Info: Conditions where there is a clear mention of security policies and procedures but with no significant deviations from standard practices; these findings may include informational value but do not pose immediate risks.

If the README doesn’t specify exact risk levels, infer them based on the scanner’s purpose and impact:

Example Findings:

  • A company website does not mention any security policy or related procedures in its documentation.
  • The trust center page lacks detailed information about how data is protected against potential breaches.
  • Compliance certifications are present but do not cover all essential aspects of information security management as per ISO 27001 standards.

Purpose: The Zero_Trust_Metrics Scanner is designed to assess the effectiveness of a company’s zero-trust strategy by evaluating its security policies, incident response procedures, data protection measures, and access control mechanisms. This tool helps in identifying gaps in maturity indicators such as SOC 2 compliance, ISO 27001 certification, penetration testing, and vulnerability assessments.

What It Detects:

  • Security Policy Indicators: The scanner identifies the presence of a security policy document, checks for incident response procedures, verifies data protection measures, and ensures access control mechanisms are in place.
  • Maturity Indicators: This includes confirming SOC 2 compliance certification, validating ISO 27001 certification, detecting penetration testing activities, and identifying vulnerability scanning or assessment processes.

Inputs Required:

  • domain (string): The primary domain to analyze, such as “acme.com.”
  • company_name (string): The company name for statement searching, such as “Acme Corporation.”

Business Impact: This scanner is crucial for organizations aiming to implement robust zero-trust architectures. By identifying gaps in security policies and maturity indicators, the scanner helps ensure compliance with industry standards and enhances overall security posture against potential threats.

Risk Levels:

  • Critical: Conditions that pose a severe risk to organizational security, such as non-compliance with mandatory security regulations or significant vulnerabilities not previously disclosed.
  • High: Conditions that significantly impact security but are less critical than those at the critical level, such as missing vulnerability assessments in high-risk areas.
  • Medium: Conditions that have moderate impact on security and may require attention to improve overall risk posture, such as incomplete access control mechanisms.
  • Low: Conditions with minimal impact on security that can be addressed later or through less urgent measures, such as minor discrepancies in data protection measures.
  • Info: Informational findings that do not directly affect security but provide insights for continuous improvement and best practices adherence.

Example Findings:

  1. The scanner might flag a company without an up-to-date incident response plan despite having robust data protection measures, indicating a critical gap in their zero-trust strategy.
  2. A lack of penetration testing records against expected threat models could be flagged as high risk if the organization operates in a highly regulated industry where compliance is mandatory.

Purpose: The Business Impact Analysis Scanner evaluates the adequacy of a company’s security policies and maturity indicators to ensure compliance with zero-trust principles. It identifies gaps in impact assessment and prioritizes recovery strategies by analyzing publicly available documentation.

What It Detects:

  • Detects mentions of “security policy” without detailed implementation.
  • Checks for comprehensive incident response plans.
  • Verifies data protection measures are adequately described.
  • Ensures access control policies are well-documented.
  • Identifies SOC 2 compliance certifications.
  • Confirms ISO/IEC 27001 standards adherence.
  • Looks for evidence of penetration testing activities.
  • Detects regular vulnerability scanning or assessment practices.
  • Scans public policy pages for security-related keywords and phrases.
  • Verifies the presence of detailed incident response procedures.
  • Checks for data protection policies that align with industry standards.
  • Ensures access control mechanisms are described in detail.
  • Analyzes trust center information for comprehensive security disclosures.
  • Looks for SOC 2 or ISO/IEC 27001 certifications mentioned.
  • Verifies penetration testing and vulnerability assessment activities.
  • Checks for detailed descriptions of data protection measures.

Inputs Required:

  • domain (string): Primary domain to analyze (e.g., acme.com)
  • company_name (string): Company name for statement searching (e.g., “Acme Corporation”)

Business Impact: This scanner is crucial as it helps in assessing the security posture of a company by evaluating its policies and maturity indicators against zero-trust principles. Identifying gaps in compliance can lead to improved security practices, enhanced trust among stakeholders, and reduced risk associated with non-compliance or inadequate security measures.

Risk Levels:

  • Critical: Conditions that directly impact critical security functions such as data protection, access control, and incident response are inadequately documented or not present at all.
  • High: There are significant gaps in the company’s security policies and practices, which could lead to high risks if exploited by malicious actors.
  • Medium: The company has some documentation but lacks detailed implementation of critical security measures as specified in standards like SOC 2 and ISO/IEC 27001.
  • Low: The company demonstrates a strong foundation in security policies and practices, with most requirements met adequately.
  • Info: Informal or supplementary security disclosures that do not significantly impact the overall risk profile but are still important for transparency.

Example Findings:

  • A company lacks a detailed security policy document that covers all critical aspects of information security.
  • The incident response plan is minimal and does not cover potential threats effectively, lacking specific recovery strategies outlined.
  • Access control mechanisms are described vaguely in the documentation, with no clear delineation of user roles and permissions.