Olivier Reuland
Pragmatic Information Security and Privacy Expert
|
Services
|
Clients
|
Posts
|
Tools
|
About
|
Contact
|
/
Assessment
/
Comprehensive
Comprehensive Security Assessment
An expanded comprehensive assessment covering APRA 234, ISO 27001, and SOC 2 requirements for enterprise-grade security management.
Comprehensive Security Assessment
An expanded comprehensive assessment covering APRA 234, ISO 27001, and SOC 2 requirements for enterprise-grade security management.
Progress: 0 of 85 questions answered
0%
1
Governance, Risk & Compliance (GRC)
Do you have a formally documented information security policy suite?
Why this matters:
Publish a governing policy suite to set management direction, scope, and accountability for the Information Security Management System (ISMS).
Yes, a comprehensive policy suite is approved by management, published, and reviewed annually.
Yes, but it is not formally approved or is outdated.
We have some informal security guidelines or a single high-level policy.
No, we do not have a documented information security policy.
Not Applicable
2
Governance, Risk & Compliance (GRC)
How does your organization manage information security risks?
Why this matters:
Implement a formal risk management process to systematically identify, analyze, and treat threats to your information assets.
We have a formal, documented risk management process that is integrated into business planning and reviewed regularly.
We periodically conduct risk assessments, but the process is not fully formalized.
We address risks in an ad-hoc manner as they are identified.
We do not have a process for managing information security risks.
Not Applicable
3
Governance, Risk & Compliance (GRC)
Are information security roles and responsibilities clearly defined and allocated?
Why this matters:
Define and assign security responsibilities to ensure accountability and prevent gaps in your security program.
Yes, all roles and responsibilities are documented in a RACI matrix and are well understood.
Some security roles are defined, but there are gaps or overlaps.
Roles are informally understood but not documented.
No defined roles or responsibilities for information security.
Not Applicable
4
Governance, Risk & Compliance (GRC)
How do you identify and comply with legal, statutory, and regulatory requirements?
Why this matters:
Maintain a structured process to identify and track obligations, preventing non-compliance penalties and legal issues.
We maintain a comprehensive register of requirements, linked to controls, which is reviewed quarterly by legal and compliance teams.
We are aware of requirements and track them, but the process is not fully formalized.
We rely on our external legal counsel or address compliance issues reactively.
We do not have a formal process for identifying or tracking compliance requirements.
Not Applicable
5
Governance, Risk & Compliance (GRC)
Do you maintain a formal Information Security Management System (ISMS)?
Why this matters:
Establish a structured ISMS to systematically manage information security risks and controls using a continuous improvement approach.
Yes, we have a certified ISMS (e.g., ISO 27001) with regular internal and external audits.
We have a formal ISMS framework, but it is not externally certified.
We have some elements of an ISMS but not a complete framework.
We do not have a formal ISMS.
Not Applicable
6
Governance, Risk & Compliance (GRC)
How does senior management demonstrate leadership and commitment to information security?
Why this matters:
Secure executive support to ensure adequate resources, accountability, and organizational prioritization of security initiatives.
Security is a standing board agenda item with executive KPIs tied to security outcomes and regular security investment reviews.
Management receives security briefings and approves major security initiatives.
Management is informed of security issues but has limited active involvement.
Limited or no visible management commitment to information security.
Not Applicable
7
Governance, Risk & Compliance (GRC)
Do you conduct regular internal audits of your information security controls?
Why this matters:
Perform internal audits to independently verify control effectiveness and identify improvement opportunities before external audits.
Yes, we have a formal internal audit program with scheduled audits, tracking of findings, and remediation verification.
We conduct informal internal assessments but lack a structured audit program.
We primarily rely on external assessments with minimal internal validation.
We do not regularly audit our security controls.
Not Applicable
8
Governance, Risk & Compliance (GRC)
How do you manage and communicate security performance metrics?
Why this matters:
Track and report security metrics to demonstrate effectiveness, identify trends, and inform decision-making.
We maintain a comprehensive security dashboard with KPIs aligned to business objectives, reviewed regularly by leadership.
We track some security metrics but lack a comprehensive measurement program.
We collect basic security data but do not have formal metrics or reporting.
We do not track security metrics.
Not Applicable
9
Human Capital Security
Are background verification checks conducted for candidates before employment?
Why this matters:
Screen personnel to reduce the risk of insider threats and to comply with legal or regulatory requirements for sensitive roles.
Yes, for all employees and contractors, based on role-specific risk.
Yes, but only for certain senior or financial roles.
We perform basic reference checks but no formal background verification.
No background checks are performed.
Not Applicable
10
Human Capital Security
Do employment and contractor agreements include information security responsibilities?
Why this matters:
Formalize security duties contractually to set clear expectations and provide a basis for enforcement.
Yes, all contracts include clear terms on confidentiality, acceptable use, and incident reporting.
Some contracts include security responsibilities, but it is not standardized.
We rely on a standard confidentiality or non-disclosure agreement (NDA).
No, contracts do not include specific security responsibilities.
Not Applicable
11
Human Capital Security
Do you provide security and privacy awareness training to your employees?
Why this matters:
Train personnel to build a security-conscious culture and reduce the risk of human error leading to incidents.
Yes, we have an ongoing program with role-based training, phishing simulations, and annual refreshers.
Yes, we conduct annual security awareness training for all staff.
Training is provided during onboarding, but there are no regular refreshers.
No formal security or privacy training is provided.
Not Applicable
12
Human Capital Security
How do you manage the information security aspects of termination or change of employment?
Why this matters:
Implement robust offboarding procedures to prevent unauthorized access from former employees and protect intellectual property.
We have a formal termination process with immediate access revocation, asset recovery, and documented acknowledgment of ongoing obligations.
We have a standard process for termination but may have delays in access revocation.
We handle terminations on a case-by-case basis without a standardized process.
We have no specific security procedures for termination.
Not Applicable
13
Human Capital Security
How do you enforce information security for remote and mobile working?
Why this matters:
Secure remote work environments to maintain information security outside the controlled office environment.
We have comprehensive remote work security controls including device management, secure access (VPN/Zero Trust), and monitored compliance.
We have basic remote work security measures like VPN and device guidelines.
We have minimal remote work security requirements with limited enforcement.
We have no specific security controls for remote workers.
Not Applicable
14
Human Capital Security
Do you have a formal disciplinary process for information security violations?
Why this matters:
Establish clear consequences for security policy violations to reinforce the importance of compliance and deter unsafe behavior.
Yes, we have a well-defined, documented process with graduated sanctions based on severity and intent, applied consistently.
We have general guidelines for handling security violations but no formal process.
Security violations are handled case-by-case without consistent guidelines.
We have no specific process for security violations.
Not Applicable
15
Asset Management
Do you maintain an inventory of your information assets?
Why this matters:
Maintain a complete and accurate inventory to ensure all assets are known and protected; you cannot protect what you do not know you have.
Yes, we have a comprehensive, automated inventory of all assets (hardware, software, data, cloud services) linked to owners.
We have inventories for different asset types (e.g., hardware, software), but they are not consolidated.
We have an incomplete or outdated inventory that is manually maintained.
We do not have a formal inventory of assets.
Not Applicable
16
Asset Management
How do you classify and handle information based on its sensitivity?
Why this matters:
Classify information to ensure that sensitive data receives an appropriate level of protection against unauthorized disclosure or modification.
We have a formal data classification policy with clear handling procedures, and classification is automated where possible.
We have a basic data classification scheme (e.g., Public, Internal, Confidential).
We handle sensitive data informally without a defined classification scheme.
We do not have a data classification system.
Not Applicable
17
Asset Management
How do you securely dispose of data and media when they are no longer needed?
Why this matters:
Dispose of data and media securely to prevent the unauthorized recovery of sensitive information from retired assets.
We have formal data destruction procedures with verification and certificates of destruction for all media types.
We have basic data deletion procedures, such as reformatting drives.
Data disposal is handled informally on a case-by-case basis.
We have no secure data or media disposal procedures.
Not Applicable
18
Asset Management
How do you manage and control the use of removable media?
Why this matters:
Control removable media to prevent data leakage and the introduction of malware through unauthorized devices.
We have technical controls to restrict and monitor removable media usage, with encryption enforced for authorized devices.
We have a policy on removable media usage but limited technical enforcement.
We have minimal controls or guidance on removable media.
We have no controls for removable media usage.
Not Applicable
19
Asset Management
How do you manage the return of assets when personnel leave the organization?
Why this matters:
Ensure all corporate assets are returned upon termination to prevent data loss and unauthorized access to organizational resources.
We have a formal asset return process with asset tracking, documented verification, and follow-up procedures for unreturned items.
We have a standard checklist for asset return but may lack verification or follow-up.
Asset return is handled informally during offboarding.
We have no specific process for asset return.
Not Applicable
20
Account & Access Management
How do you manage user identity and control access to systems and data?
Why this matters:
Enforce least-privilege access to reduce the risk of unauthorized data access, modification, or destruction.
We use a centralized identity provider (SSO) with role-based access control (RBAC) and conduct quarterly access reviews.
We have basic access controls, but they are managed separately for each system.
Access is granted based on informal requests with limited restrictions.
We do not have specific data access controls; access is largely open.
Not Applicable
21
Account & Access Management
Do you use multi-factor authentication (MFA) to protect accounts?
Why this matters:
Deploy MFA to significantly reduce the risk of account takeover from stolen credentials, which is a leading cause of breaches.
MFA is required for all users, on all systems, using phishing-resistant methods (e.g., FIDO2/WebAuthn).
MFA is required for all users, but may include weaker methods like SMS.
MFA is required for privileged accounts but is optional for standard users.
No MFA is implemented, or it is entirely optional.
Not Applicable
22
Account & Access Management
How do you manage privileged (administrative) accounts?
Why this matters:
Apply strict controls to privileged accounts, as their compromise can lead to a complete loss of confidentiality, integrity, and availability.
We use a Privileged Access Management (PAM) solution for Just-in-Time (JIT) access with session recording.
Privileged accounts are separate from standard user accounts and require MFA.
We have some privileged accounts that are shared or used for daily tasks.
We do not have specific controls for privileged accounts.
Not Applicable
23
Account & Access Management
What is your process for onboarding and offboarding users (Joiners, Movers, Leavers)?
Why this matters:
Implement a robust JML process to ensure access is granted on a least-privilege basis and revoked promptly to prevent misuse.
We have a fully automated process tied to our HR system that provisions and de-provisions access based on roles.
We have a documented, checklist-driven process, and access is revoked within 24 hours of departure.
Our process is manual and informal, which can lead to delays in revoking access.
We have no formal process for managing user accounts through their lifecycle.
Not Applicable
24
Account & Access Management
How do you review and validate user access rights?
Why this matters:
Conduct regular access reviews to identify and remediate inappropriate access, access creep, and orphaned accounts.
We conduct quarterly attestations of all access rights with automated tools and track remediation of identified issues.
We conduct annual access reviews for critical systems.
We review access on an ad hoc basis or when issues arise.
We do not regularly review user access rights.
Not Applicable
25
Account & Access Management
How do you manage and secure user passwords?
Why this matters:
Implement strong password policies and secure storage practices to reduce the risk of credential-based attacks.
We enforce NIST-compliant password policies with secure storage (salted hashing), breach detection, and password managers.
We have standard password complexity requirements and hashed storage.
We have basic password requirements but limited enforcement.
We have minimal or no password requirements.
Not Applicable
26
Account & Access Management
How do you secure remote access to your network and systems?
Why this matters:
Implement strong remote access controls to prevent unauthorized access to internal resources from external networks.
We use a Zero Trust architecture with device posture checks, MFA, and least-privilege access for all remote connections.
We use a VPN with MFA for remote access to internal resources.
We have basic remote access controls with limited security requirements.
Remote access has minimal security controls.
Not Applicable
27
Data Protection & Privacy
Do you encrypt sensitive data both in transit and at rest?
Why this matters:
Encrypt sensitive data to render it unusable to unauthorized parties in case of a breach of storage or network infrastructure.
Yes, all sensitive data is encrypted using strong, modern algorithms with secure key management.
Encryption is applied to most sensitive data, often using provider defaults.
Some, but not all, sensitive data is encrypted.
No encryption is implemented for sensitive data.
Not Applicable
28
Data Protection & Privacy
How does your organization document and communicate its privacy practices (collection, use, protection of customer data)?
Why this matters:
Publish and maintain a clear privacy policy to build user trust and satisfy legal obligations (e.g., GDPR, CCPA).
Yes, our privacy policy is comprehensive, written in plain language, and updated regularly with proactive communication to users.
Yes, but the policy is outdated or difficult to understand.
A basic, template-based privacy policy exists.
We do not have a public privacy policy.
Not Applicable
29
Data Protection & Privacy
Do you provide customers with ways to exercise their data subject rights (e.g., access, update, delete their data)?
Why this matters:
Enable and fulfill Data Subject Access Requests (DSARs) to meet legal mandates (e.g., GDPR "right to erasure") and strengthen user trust.
Yes, we have a self-service portal and documented internal processes with strict SLAs for fulfillment.
Yes, but it requires users to contact support via email, and the process is manual.
We handle requests on an ad-hoc basis with no formal process.
We do not have an established process to handle data subject requests.
Not Applicable
30
Data Protection & Privacy
Do you have data backup and recovery procedures?
Why this matters:
Maintain reliable, tested backups as a final line of defense against data loss from ransomware, hardware failure, or human error.
Yes, we have automated daily backups that are stored off-site/isolated, with quarterly, documented recovery tests.
We have regular automated backups but rarely test the recovery process.
We perform occasional or manual backups of critical data.
We have no regular or reliable backup procedures.
Not Applicable
31
Data Protection & Privacy
How do you prevent data leakage from your systems?
Why this matters:
Implement data loss prevention controls to protect sensitive information from unauthorized exfiltration.
We use comprehensive DLP solutions across endpoints, networks, and cloud services with content inspection and behavioral analytics.
We have some DLP controls for specific channels or sensitive data types.
We have basic controls like email attachment limits but no formal DLP solution.
We have no specific controls to prevent data leakage.
Not Applicable
32
Data Protection & Privacy
How do you ensure compliance with data protection regulations?
Why this matters:
Maintain a privacy compliance program to meet legal requirements, protect customer data, and avoid regulatory penalties.
We have a comprehensive privacy program with dedicated staff, regular assessments, and a roadmap aligned to changing regulations.
We have implemented basic privacy compliance measures for major regulations affecting our business.
We address privacy compliance reactively when issues arise.
We have minimal privacy compliance measures in place.
Not Applicable
33
Data Protection & Privacy
How do you manage and minimize personal data collection?
Why this matters:
Implement data minimization to reduce privacy risk, comply with regulations, and limit exposure in case of a breach.
We apply data minimization principles by design, with formal processes for justifying all data collection and regular data minimization reviews.
We have guidelines for data minimization but no formal processes for enforcement.
We consider data minimization informally.
We have no specific practices for data minimization.
Not Applicable
34
Data Protection & Privacy
How do you manage data retention and deletion?
Why this matters:
Implement data retention policies to ensure data is kept only as long as necessary and then securely deleted.
We have a comprehensive data retention program with automated enforcement, secure deletion, and regular compliance auditing.
We have retention policies for key data types but limited automation or verification.
We have some informal guidelines but no formal retention policy.
We do not have specific data retention practices.
Not Applicable
35
Network Security
How do you protect your network perimeter?
Why this matters:
Deploy perimeter controls to block commodity attacks and provide a first line of defense against targeted intrusions.
We use a next-generation firewall (NGFW) with advanced threat protection (IPS, malware sandboxing) and egress filtering.
We use a stateful firewall with access control lists (ACLs).
We rely on basic firewall capabilities of our router or cloud security groups.
We do not have a dedicated firewall protecting our network.
Not Applicable
36
Network Security
How do you segment your network to prevent lateral movement?
Why this matters:
Segment networks to contain breaches, limiting an attacker's ability to move from a compromised host to critical assets.
We use micro-segmentation to enforce strict access controls between individual workloads and applications.
We have separate network zones (VLANs/VPCs) for servers, users, and development environments.
We have a basic guest network that is separate from our corporate network.
We have a flat network with no internal segmentation.
Not Applicable
37
Network Security
How do you secure your wireless networks?
Why this matters:
Harden wireless networks to prevent unauthorized access to your internal network and protect data from being intercepted.
We use WPA3-Enterprise with 802.1X authentication, and guest/corporate traffic is strictly segregated.
We use WPA2/WPA3 with a strong, complex pre-shared key (PSK).
We use WPA2 with a simple, shared password.
Our network uses WEP, is open (unsecured), or we use the default password.
Not Applicable
38
Network Security
How do you detect and prevent network-based attacks?
Why this matters:
Implement intrusion detection and prevention to identify and block malicious network activity before it causes damage.
We use IDS/IPS systems with regular signature updates, network behavior analysis, and 24/7 monitoring.
We have basic IDS/IPS systems deployed at key network points.
We have limited or passive network monitoring without active prevention.
We have no specific controls for detecting network-based attacks.
Not Applicable
39
Network Security
How do you secure remote network connections to your environment?
Why this matters:
Implement secure remote access to protect sensitive data and prevent unauthorized access to internal resources.
We use a Zero Trust model with strong authentication, device health validation, and least-privilege access controls.
We use a VPN with MFA and basic security policies for remote connections.
We have a basic VPN solution with password authentication.
We allow remote connections with minimal security controls.
Not Applicable
40
End-User Device Security
How do you secure laptops and mobile devices (endpoints) used for work?
Why this matters:
Harden endpoints to protect corporate data and prevent them from becoming an entry point for attackers into your network.
We use a unified endpoint management (UEM/MDM) solution to enforce full disk encryption, security policies, and remote wipe capabilities.
We have basic device security measures, like requiring passwords and antivirus software.
We provide guidelines to users but do not technically enforce security controls.
We have no specific security measures for end-user devices.
Not Applicable
41
End-User Device Security
How do you protect work devices from malware?
Why this matters:
Deploy endpoint protection to detect and block malware, preventing credential theft, data destruction, and ransomware.
We use a centrally managed Endpoint Detection and Response (EDR) solution with real-time monitoring and threat hunting.
We use a centrally managed enterprise antivirus (AV) solution.
Users have basic, unmanaged antivirus software installed.
We have no antivirus or malware protection on endpoints.
Not Applicable
42
End-User Device Security
Do you control what software can be installed on work devices?
Why this matters:
Control software installations to reduce the attack surface, prevent malware, and avoid licensing issues from unapproved "shadow IT" applications.
We use application control (whitelisting) to allow only approved software to be executed.
Users do not have administrative rights, which restricts most software installations.
We have a policy about software installation, but it is not technically enforced.
There are no controls; users can install any software they want.
Not Applicable
43
End-User Device Security
How do you manage and secure mobile devices used for business purposes?
Why this matters:
Implement mobile device security to protect corporate data accessed or stored on smartphones and tablets.
We use an enterprise mobility management (EMM) solution with containerization, security policies, and remote management capabilities.
We have basic MDM features deployed to corporate devices with some security policies.
We have minimal controls or guidelines for mobile device usage.
We have no specific controls for mobile devices.
Not Applicable
44
End-User Device Security
How do you secure your BYOD (Bring Your Own Device) environment?
Why this matters:
Implement BYOD controls to protect corporate data on employee-owned devices while respecting user privacy.
We use a comprehensive BYOD solution with containerization, conditional access, and clear separation of personal and corporate data.
We have basic BYOD management with some security requirements for personal devices.
We allow BYOD with minimal security controls or guidelines.
We have no specific controls for BYOD usage.
Not Applicable
45
Cryptography
How do you manage cryptographic keys in your environment?
Why this matters:
Implement secure key management to protect the confidentiality and integrity of encrypted data and prevent unauthorized access.
We use a dedicated key management system with hardware security modules (HSMs), key rotation, and strict access controls.
We manage keys using built-in platform features with some manual processes.
Key management is ad hoc with limited documentation or controls.
We have no formal key management practices.
Not Applicable
46
Cryptography
What encryption standards and algorithms do you use?
Why this matters:
Implement strong, modern encryption to protect sensitive data from unauthorized access and meet compliance requirements.
We use industry-standard encryption (AES-256, RSA-2048+, ECC) with regular review against evolving standards and vulnerabilities.
We use standard encryption algorithms but have limited documentation or review processes.
We use some encryption but lack standardization across our environment.
We have minimal or ad hoc encryption practices.
Not Applicable
47
Cryptography
How do you secure transport layer communications?
Why this matters:
Implement secure transport protocols to protect data in transit from interception, tampering, or eavesdropping.
We enforce TLS 1.2+ with strong cipher suites, certificate validation, and monitoring for all network communications.
We use TLS for most services but may have inconsistent implementation or older versions.
We use encryption for some transport layer communications but lack a consistent approach.
We have minimal transport encryption or use outdated protocols.
Not Applicable
48
Cryptography
How do you manage digital certificates in your environment?
Why this matters:
Implement secure certificate management to prevent service outages, man-in-the-middle attacks, and unauthorized access.
We use a certificate lifecycle management system with automated monitoring, renewal, and inventory.
We maintain a certificate inventory with manual monitoring and renewal processes.
We track certificates informally with minimal automation.
We have no formal certificate management practices.
Not Applicable
49
Threat & Vulnerability Management
How do you manage security patches for operating systems and applications?
Why this matters:
Patch vulnerabilities promptly to close security gaps before they can be exploited by attackers, as this is a primary infection vector.
We use a centralized, automated patch management system that applies critical patches within 48 hours, with compliance reporting.
We have a regular monthly patching process for major systems.
We apply patches occasionally or when a problem occurs.
We do not have a regular process for applying security patches.
Not Applicable
50
Threat & Vulnerability Management
Do you scan your systems and applications for security vulnerabilities?
Why this matters:
Perform regular vulnerability scanning to proactively identify and remediate weaknesses in your environment before they can be exploited.
Yes, we perform authenticated scans on all assets weekly, with results fed into a remediation tracking system with strict SLAs.
We run periodic (e.g., quarterly) vulnerability scans on external and internal systems.
We perform occasional, ad-hoc vulnerability scans.
We do not perform vulnerability scanning.
Not Applicable
51
Threat & Vulnerability Management
How do you conduct security testing of your applications and infrastructure?
Why this matters:
Perform security testing to identify vulnerabilities that automated scanning might miss and validate the effectiveness of your security controls.
We conduct regular penetration tests, red team exercises, and tabletop simulations by qualified internal/external testers.
We perform annual penetration tests of key systems.
We conduct limited or ad hoc security testing.
We do not perform security testing beyond basic vulnerability scanning.
Not Applicable
52
Threat & Vulnerability Management
How do you track and manage security vulnerabilities once identified?
Why this matters:
Implement a vulnerability management process to ensure timely remediation based on risk and prevent security gaps from remaining open.
We use a vulnerability management platform with risk-based prioritization, SLAs, and integration with IT workflows.
We track vulnerabilities in a centralized system with basic prioritization and remediation tracking.
We track vulnerabilities informally with inconsistent follow-up.
We have no formal process for tracking or remediating vulnerabilities.
Not Applicable
53
Development Practices
How do you ensure security is integrated into your software development lifecycle (SDLC)?
Why this matters:
Integrate security into every phase of the SDLC ("Shift Left") to build more secure applications and reduce the cost of fixing vulnerabilities.
We have a mature Secure SDLC, including threat modeling, secure coding standards, automated security testing (SAST/DAST/SCA), and security reviews.
We conduct security reviews or penetration tests just before release.
We have some informal security considerations during development.
Security is not a formal part of our development process.
Not Applicable
54
Development Practices
How do you manage vulnerabilities in third-party software components and libraries?
Why this matters:
Manage open-source and third-party components proactively, as vulnerabilities in these dependencies are a major source of application risk.
We use a Software Composition Analysis (SCA) tool to automatically scan dependencies, block builds with critical vulnerabilities, and generate SBOMs.
We periodically scan our applications for vulnerable dependencies.
We update our dependencies on an ad-hoc basis.
We do not have a process for managing third-party vulnerabilities.
Not Applicable
55
Development Practices
How do you protect sensitive data like API keys, credentials, and tokens in your development process?
Why this matters:
Prevent hard-coded secrets in source code, which can be easily exposed and lead to system compromise.
We use a centralized secret management solution (e.g., Vault, AWS/GCP/Azure KMS) with automated rotation and granular access controls.
Secrets are stored in environment variables or secure configuration files.
Secrets are sometimes stored in source code, but in private repositories.
We have no specific process; secrets are often stored in plain text in code or config files.
Not Applicable
56
Development Practices
How do you conduct security testing during the development process?
Why this matters:
Implement security testing throughout development to identify and fix vulnerabilities before they reach production.
We integrate automated security testing (SAST, DAST, SCA, IAST) in our CI/CD pipeline with security gates that block vulnerable code.
We run some automated security testing tools periodically during development.
We rely primarily on manual code reviews for security issues.
We have minimal or no security testing during development.
Not Applicable
57
Development Practices
How do you ensure secure configuration in your development and deployment environments?
Why this matters:
Implement secure configuration management to prevent misconfigurations that could introduce vulnerabilities.
We use infrastructure as code with automated security scanning, version control, and change management for all configurations.
We have standardized configurations with some automation and version control.
We have basic configuration templates but limited automation or validation.
We configure systems manually with minimal standardization.
Not Applicable
58
Development Practices
How do you manage segregation between development, testing, and production environments?
Why this matters:
Implement environment segregation to prevent unauthorized changes and testing issues from affecting production systems.
We maintain complete logical and access separation between environments with formal promotion processes and controls.
We have separate environments with some access controls but limited formal processes.
We have separate environments but with shared access or infrastructure.
We have minimal separation between development and production.
Not Applicable
59
Security Operations & Monitoring
Do you collect and analyze logs from your systems and applications?
Why this matters:
Maintain and analyze security logs to enable the detection of suspicious activity, support incident investigations, and meet compliance obligations.
Yes, logs from all critical assets are centralized in a SIEM, correlated with threat intelligence, and actively monitored with automated alerts.
We collect logs from key systems (e.g., firewalls, domain controllers) and review them periodically.
Logging is enabled on some systems, but logs are not centralized or regularly reviewed.
Logging is not systematically enabled or collected.
Not Applicable
60
Security Operations & Monitoring
How do you monitor for security events and incidents?
Why this matters:
Implement security monitoring to detect and respond to threats quickly, minimizing the impact of security incidents.
We have 24/7 security monitoring with automated and manual analysis, tuned detection rules, and threat hunting.
We have basic security monitoring with automated alerts for known threat patterns.
We have limited monitoring capabilities focused on specific systems or events.
We have minimal or no security monitoring.
Not Applicable
61
Security Operations & Monitoring
How do you protect and validate the integrity of your logs?
Why this matters:
Secure logs to prevent tampering and ensure they can be used as reliable evidence for security investigations and compliance.
We use write-once storage, cryptographic verification, and real-time monitoring for log tampering attempts.
Logs are centralized with access controls and basic integrity protection.
Logs are collected centrally but have limited protection against tampering.
Logs are stored locally with minimal protection.
Not Applicable
62
Security Operations & Monitoring
How do you conduct threat hunting in your environment?
Why this matters:
Implement proactive threat hunting to discover adversaries who have evaded automated detection systems.
We conduct regular, hypothesis-driven threat hunting based on current threats and the MITRE ATT&CK framework.
We perform occasional threat hunting focused on specific threats or vulnerabilities.
We investigate suspicious activity but do not conduct proactive hunting.
We do not conduct threat hunting activities.
Not Applicable
63
Security Operations & Monitoring
How do you use threat intelligence to enhance your security operations?
Why this matters:
Leverage threat intelligence to better understand adversaries, prioritize defenses, and enhance detection capabilities.
We integrate diverse threat intelligence sources with automated consumption, enrichment, and application to security controls.
We consume threat intelligence feeds and manually apply insights to our security operations.
We review general threat reports but have limited formal integration with operations.
We make minimal or no use of threat intelligence.
Not Applicable
64
Incident Response
Do you have a documented incident response plan?
Why this matters:
Maintain a structured plan to ensure a coordinated, effective, and timely response to security incidents, minimizing operational and financial impact.
Yes, we have a comprehensive plan based on a standard framework (e.g., NIST), with defined roles, which is tested biannually.
We have a basic incident response plan, but it has not been tested.
We have some informal procedures or an ad-hoc approach to incidents.
We do not have an incident response plan.
Not Applicable
65
Incident Response
How do you learn from security incidents to improve your defenses?
Why this matters:
Conduct blameless post-incident reviews to identify root causes and drive systemic improvements, preventing the recurrence of similar incidents.
We conduct a formal post-incident review for every incident, tracking all remediation actions to completion.
We conduct basic analysis after major incidents.
Learning from incidents is informal and not documented.
We do not have a systematic process for learning from incidents.
Not Applicable
66
Incident Response
How do you test your incident response capabilities?
Why this matters:
Test incident response procedures to validate effectiveness and build team experience before a real incident occurs.
We conduct a variety of exercises including tabletops, simulations, and full-scale technical response drills involving all stakeholders.
We conduct basic tabletop exercises annually.
We have conducted limited or informal testing of our response procedures.
We do not test our incident response capabilities.
Not Applicable
67
Incident Response
How do you handle external communications during security incidents?
Why this matters:
Manage communications effectively to meet regulatory requirements, maintain stakeholder trust, and control messaging.
We have a comprehensive crisis communication plan with predefined templates, spokesperson training, and regulatory notification procedures.
We have basic procedures for external communications during incidents.
We handle external communications on an ad hoc basis during incidents.
We have no specific plan for external communications during incidents.
Not Applicable
68
Incident Response
How do you preserve evidence during security incidents?
Why this matters:
Implement proper evidence handling to support investigation, maintain legal admissibility, and facilitate root cause analysis.
We have formal forensic procedures with chain of custody documentation, secure storage, and qualified personnel.
We have basic evidence collection procedures but limited formal documentation.
We make some effort to preserve evidence but lack formal procedures.
We have no specific procedures for evidence preservation.
Not Applicable
69
Business Continuity & Disaster Recovery
Do you have business continuity and disaster recovery plans?
Why this matters:
Develop and maintain plans to ensure continued operations and timely recovery from disruptive incidents.
Yes, we have comprehensive BC/DR plans based on business impact analysis, with defined recovery objectives and regular testing.
We have basic BC/DR plans, but they are not regularly tested or updated.
We have informal recovery procedures for some systems.
We do not have BC/DR plans.
Not Applicable
70
Business Continuity & Disaster Recovery
How do you test your business continuity and recovery capabilities?
Why this matters:
Test recovery plans to validate effectiveness, identify gaps, and build team experience before a real disaster.
We conduct regular tests including tabletops, functional exercises, and full-scale failover tests with measured recovery times.
We conduct annual tabletop exercises and limited technical testing.
We have conducted limited or informal testing of our recovery procedures.
We do not test our BC/DR capabilities.
Not Applicable
71
Business Continuity & Disaster Recovery
How do you ensure the security of systems during a disaster recovery situation?
Why this matters:
Maintain security controls during recovery to prevent compromises while normal defenses may be weakened.
Security requirements are fully integrated into BC/DR plans with specific controls for recovery environments and heightened monitoring.
We maintain basic security controls during recovery but may have some exceptions.
Security during recovery is considered but not formally documented.
We have not specifically addressed security during recovery scenarios.
Not Applicable
72
Business Continuity & Disaster Recovery
How do you maintain resilience for critical systems and data?
Why this matters:
Implement resilience measures to reduce the likelihood of outages and minimize the impact when they occur.
We have multi-region redundancy with automated failover, regular resilience testing, and continuous availability monitoring.
We have basic redundancy for critical systems and regular backups.
We have some redundancy measures but limited automation or testing.
We have minimal resilience measures beyond basic backups.
Not Applicable
73
Physical & Environmental Security
How do you control physical access to your facilities and sensitive areas?
Why this matters:
Implement physical access controls to prevent unauthorized access to facilities, equipment, and sensitive information.
We use electronic access systems with multi-factor authentication, monitoring, and regular access reviews for all facilities.
We have basic electronic access controls with some monitoring capabilities.
We have minimal physical security measures like locks and keys.
We have no formal physical access controls beyond basic building security.
Not Applicable
74
Physical & Environmental Security
How do you protect your equipment from environmental threats and power disruptions?
Why this matters:
Implement environmental controls to protect equipment from damage and prevent service disruptions.
We have comprehensive environmental controls including redundant power, cooling, fire suppression, and water detection with 24/7 monitoring.
We have basic environmental controls including UPS systems and fire detection.
We have minimal environmental protections with limited monitoring.
We have no specific environmental controls for our equipment.
Not Applicable
75
Physical & Environmental Security
How do you secure equipment when it is being transported or used outside your premises?
Why this matters:
Implement controls for equipment used outside your facilities to prevent theft, unauthorized access, or data exposure.
We have comprehensive policies for off-site equipment with encryption, tracking, remote wipe capabilities, and secure transport procedures.
We have basic security requirements for off-site equipment including encryption and physical security guidelines.
We have minimal controls for equipment used outside our premises.
We have no specific controls for off-site equipment.
Not Applicable
76
Physical & Environmental Security
How do you maintain a clean desk policy and screen security?
Why this matters:
Implement clean desk and clear screen policies to prevent unauthorized access to sensitive information left unattended.
We enforce a comprehensive clean desk policy with regular compliance checks, automatic screen locking, and secure document disposal.
We have a clean desk policy and screen locking requirements but limited enforcement.
We have basic guidelines but minimal formal requirements or enforcement.
We have no clean desk or screen security requirements.
Not Applicable
77
Cloud Security
How do you secure your cloud environments and services?
Why this matters:
Implement cloud security controls to protect data and workloads in cloud environments from unauthorized access and data breaches.
We use a comprehensive cloud security framework with automated policy enforcement, continuous monitoring, and security-as-code practices.
We have cloud security policies and basic security tooling for our cloud environments.
We apply some security controls to our cloud services but lack a comprehensive approach.
We have minimal security controls specific to our cloud environments.
Not Applicable
78
Cloud Security
How do you manage identity and access in cloud environments?
Why this matters:
Implement strong cloud IAM controls to prevent unauthorized access and privilege escalation in cloud environments.
We use centralized identity management with MFA, JIT access, and automated access reviews for all cloud services.
We have basic IAM controls with role-based access but limited automation or monitoring.
We manage cloud identities individually with inconsistent controls across services.
We have minimal IAM controls specific to cloud environments.
Not Applicable
79
Cloud Security
How do you secure data in cloud storage services?
Why this matters:
Implement cloud storage security to protect sensitive data from unauthorized access, leakage, or breaches.
We use comprehensive cloud storage security with encryption, access controls, monitoring, and data loss prevention.
We have basic security controls for cloud storage including encryption and access restrictions.
We apply minimal security controls to cloud storage services.
We have no specific security controls for cloud storage.
Not Applicable
80
Cloud Security
How do you monitor and respond to security events in cloud environments?
Why this matters:
Implement cloud security monitoring to detect and respond to threats specific to cloud environments.
We have comprehensive cloud security monitoring integrated with our SIEM, with automated alerting and response capabilities.
We monitor basic cloud security logs and have some alerting configured.
We have limited monitoring of cloud security events.
We have minimal or no monitoring specific to cloud environments.
Not Applicable
81
Cloud Security
How do you secure cloud infrastructure and configurations?
Why this matters:
Implement secure configuration and infrastructure management to prevent misconfigurations that could lead to breaches.
We use infrastructure as code with security validation, configuration management, and continuous compliance monitoring.
We have some infrastructure automation and configuration baselines for cloud services.
We manually configure cloud services with some security guidelines.
We have no standardized approach to cloud configuration security.
Not Applicable
82
Vendor & Third-Party Risk Management
How do you assess and manage security risks from third-party vendors?
Why this matters:
Implement vendor risk management to identify and mitigate security risks from third parties who have access to your systems or data.
We have a comprehensive vendor risk management program with tiered assessments, continuous monitoring, and regular reassessments.
We conduct security assessments for critical vendors before engagement and periodically thereafter.
We perform basic security reviews for some vendors but lack a consistent approach.
We have minimal or no vendor security assessment processes.
Not Applicable
83
Vendor & Third-Party Risk Management
How do you address security in contracts with third parties?
Why this matters:
Include security requirements in contracts to establish expectations, obligations, and remedies for security issues.
We have comprehensive security requirements in all contracts with right-to-audit clauses, SLAs, and incident notification requirements.
We include basic security language in contracts for critical vendors.
We have minimal security requirements in vendor contracts.
We do not specifically address security in vendor contracts.
Not Applicable
84
Vendor & Third-Party Risk Management
How do you manage ongoing security monitoring of third parties?
Why this matters:
Implement continuous monitoring to identify changes in vendor security posture or new risks that emerge over time.
We use a combination of continuous technical monitoring, periodic reassessments, and security rating services for ongoing oversight.
We conduct periodic reassessments and review security reports from critical vendors.
We have limited ongoing monitoring of vendor security.
We do not actively monitor vendor security posture after initial assessment.
Not Applicable
85
Vendor & Third-Party Risk Management
How do you manage security for vendor access to your systems and data?
Why this matters:
Implement vendor access controls to ensure third parties can only access what they need and activities are monitored.
We use just-in-time access with MFA, session recording, and comprehensive monitoring for all vendor access.
We have specific access controls for vendors including MFA and limited privileges.
We have basic controls for vendor access but limited monitoring or restrictions.
We have minimal controls specific to vendor access.
Not Applicable
Please answer all 85 remaining questions.
Submit Assessment