CIS Critical Security Controls Navigator

Use this page to learn more about the Controls and Safeguards and see how they map to other security standards. Click on a row to see all related, applicable standards.

Mappings - (0)

Add Remove All

No mappings selected

CSA Cloud Controls Matrix v4 
0 / 197 selected   Deselect All Select All
Revert       Remove
Background Screening Policy and Procedures
Audit and Assurance Policy and Procedures
Independent Assessments
Risk Based Planning Assessment
Requirements Compliance
Audit Management Process
This one is missing from mapping
Application and Interface Security Policy and Procedures
Application Security Baseline Requirements
Application Security Metrics
Secure Application Design and Development
Automated Application Security Testing
Automated Secure Application Deployment
Application Vulnerability Remediation
Business Continuity Management Policy and Procedures
Risk Assessment and Impact Analysis
Business Continuity Strategy
Business Continuity Planning
Business Continuity Exercises
Disaster Response Plan
Response Plan Exercise
Equipment Redundancy
Change Management Policy and Procedures
Quality Testing
Change Management Technology
Unauthorized Change Protection
Change Agreements
Change Management Baseline
Detection of Baseline Deviation
Exception Management
Change Restoration
Encryption and Key Management Policy and Procedures
CEK Roles and Responsibilities
Data Encryption
Encryption Algorithm
Encryption Change Management
Encryption Change Cost Benefit Analysis
Encryption Risk Management
CSC Key Management Capabiility
Encryption and Key Management Audit
Key Generation
Key Purpose
Key Rotation
Key Revocation
Key Destruction
Key Activation
Key Suspension
Key Deactivation
Key Archival
Key Compromise
Key Recovery
Key Inventory Management
Off-Site Equipment Disposal Policy and Procedures
Off-Site Transfer Authorization Policy and Procedures
Secure Area Policy and Procedures
Secure Media Transportation Policy and Procedures
Assets Classification
Assets Cataloguing and Tracking
Controlled Access Points
Equipment Identification
Secure Area Authorization
Surveillance System
Unauthorized Access Response Training
Cabling Security
Environmental Systems
Secure Utilities
Equipment Location
Security and Privacy Policy and Procedures
Secure Disposal
Data Inventory
Data Classification
Data Flow Documentation
Data Ownership and Stewardship
Data Protection by Design and Default
Data Privacy by Design and Default
Data Protection Impact Assessment
Personal Data Access, Reversal, Rectification and Deletion
Limitation of Purpose in Personal Data Processing
Personal Data Sub-processing
Disclosure of Data Sub-processors
Limitation of Production Data Use
Data Retention and Deletion
Sensitive Data Protection
Disclosure Notification
Data Location
Governance Program Policy and Procedures
Risk Management Program
Organizational Policy Reviews
Policy Exception Process
Information Security Program
Governance Responsibility Model
Information System Regulatory Mapping
Special Interest Groups
Acceptable Use of Technology Policy and Procedures
Clean Desk Policy and Procedures
Remote and Home Working Policy and Procedures
Asset returns
Employment Termination
Employment Agreement Process
Employment Agreement Content
Personnel Roles and Responsibilities
Non-Disclosure Agreements
Security Awareness Training
Personal and Sensitive Data Awareness and Training
Compliance User Responsibility
Identity and Access Management Policy and Procedures
Strong Password Policy and Procedures
Identity Inventory
Separation of Duties
Least Privilege
User Access Provisioning
User Access Changes and Revocation
User Access Review
Segregation of Privileged Access Roles
Management of Privileged Access Roles
CSCs Approval for Agreed Privileged Access Roles
Safeguard Logs Integrity
Uniquely Identifiable Users
Strong Authentication
Passwords Management
Authorization Mechanisms
Interoperability and Portability Policy and Procedures
Application Interface Availability
Secure Interoperability and Portability Management
Data Portability Contractual Obligations
Infrastructure and Virtualization Security Policy and Procedures
Capacity and Resource Planning
Network Security
OS Hardening and Base Controls
Production and Non-Production Environments
Segmentation and Segregation
Migration to Cloud Environments
Network Architecture Documentation
Network Defense
Logging and Monitoring Policy and Procedures
Audit Logs Protection
Security Monitoring and Alerting
Audit Logs Access and Accountability
Audit Logs Monitoring and Response
Clock Synchronization
Logging Scope
Log Records
Log Protection
Encryption Monitoring and Reporting
Transaction/Activity Logging
Access Control Logs
Failures and Anomalies Reporting
Security Incident Management Policy and Procedures
Service Management Policy and Procedures
Incident Response Plans
Incident Response Testing
Incident Response Metrics
Event Triage Processes
Security Breach Notification
Points of Contact Maintenance
SSRM Policy and Procedures
SSRM Supply Chain
SSRM Guidance
SSRM Control Ownership
SSRM Documentation Review
SSRM Control Implementation
Supply Chain Inventory
Supply Chain Risk Management
Primary Service and Contractual Agreement
Supply Chain Agreement Review
Internal Compliance Testing
Supply Chain Service Agreement Compliance
Supply Chain Governance Review
Supply Chain Data Security Assessment
Threat and Vulnerability Management Policy and Procedures
Malware Protection Policy and Procedures
Vulnerability Remediation Schedule
Detection Updates
External Library Vulnerabilities
Penetration Testing
Vulnerability Identification
Vulnerability Prioritization
Vulnerability Management Reporting
Vulnerability Management Metrics
Endpoint Devices Policy and Procedures
Endpoint Inventory
Endpoint Management
Automatic Lock Screen
Operating Systems
Storage Encryption
Anti-Malware Detection and Prevention
Software Firewall
Data Loss Prevention
Remote Locate
Remote Wipe
Third-Party Endpoint Security Posture
0 / 173 selected   Deselect All Select All
Revert       Remove
Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).
Limit information system access to the types of transactions and functions that authorized users are permitted to execute.
Verify and control/limit connections to and use of external information systems.
Control information posted or processed on publicly accessible information systems.
Provide privacy and security notices consistent with applicable CUI rules.
Limit use of portable storage devices on external systems.
Employ the principle of least privilege, including for specific security functions and privileged accounts.
Use non-privileged accounts or roles when accessing nonsecurity functions.
Limit unsuccessful logon attempts.
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
Authorize wireless access prior to allowing such connections.
Monitor and control remote access sessions.
Route remote access via managed access control points.
Control the flow of CUI in accordance with approved authorizations.
Protect wireless access using authentication and encryption.
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
Control connection of mobile devices.
Authorize remote execution of privileged commands and remote access to security relevant information.
Encrypt CUI on mobile devices and mobile computing platforms.
Control information flows between security domains on connected systems.
Periodically review and update CUI program access permissions.
Restrict remote network access based on organizationally defined risk factors such as time of day, location of access, physical location, network connection state, and measured properties of the current user and role.
Identify and mitigate risk associated with unidentified wireless access points connected to the network.
Define procedures for the handling of CUI data.
Employ a capability to discover and identify systems with specific component attributes (e.g., firmware level, OS type) within your inventory.
Ensure that managers, system administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems.
Ensure that personnel are trained to carry out their assigned information security related duties and responsibilities.
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
Provide awareness training focused on recognizing and responding to threats from social engineering, advanced persistent threat actors, breaches, and suspicious behaviors; update the training at least annually or when there are significant changes to the threat.
Include practical exercises in awareness training that are aligned with current threat scenarios and provide feedback to individuals involved in the training.
Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.
Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
Review audit logs.
Review and update logged events.
Alert in the event of an audit logging process failure.
Collect audit information (e.g., logs) into one or more central repositories.
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
Limit management of audit logging functionality to a subset of privileged users.
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
Provide audit record reduction and report generation to support on-demand analysis and reporting.
Automate analysis of audit logs to identify and act on critical indicators (TTPs) and/or organizationally defined suspicious activity.
Review audit information for broad activity in addition to per-machine activity.
Identify assets not reporting audit logs and assure appropriate organizationally defined systems are logging.
Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
Employ a security assessment of enterprise software that has been developed internally, for internal use, and that has been organizationally defined as an area of risk.
Create, maintain, and leverage a security strategy and roadmap for organizational cybersecurity improvement.
Conduct penetration testing periodically, leveraging automated scanning tools and ad hoc tests using human experts.
Periodically perform red teaming against organizational assets in order to validate defensive capabilities.
Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
Control and monitor user installed software.
Establish and enforce security configuration settings for information technology products employed in organizational systems.
Track, review, approve, or disapprove, and log changes to organizational systems.
Analyze the security impact of changes prior to implementation.
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permitby- exception (whitelisting) policy to allow the execution of authorized software.
Employ application whitelisting and an application vetting process for systems identified by the organization.
Verify the integrity and correctness of security critical or essential software as defined by the organization (e.g., roots of trust, formal verification, or cryptographic signatures).
Identify information system users, processes acting on behalf of users, or devices.
Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.
Enforce a minimum password complexity and change of characters when new passwords are created.
Prohibit password reuse for a specified number of generations.
Allow temporary password use for system logons with an immediate change to a permanent password.
Store and transmit only cryptographically-protected passwords.
Obscure feedback of authentication information.
Use multifactor authentication for local and network access to privileged accounts and for network access to nonprivileged accounts.
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
Prevent the reuse of identifiers for a defined period.
Disable identifiers after a defined period of inactivity.
Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
Detect and report events.
Develop and implement responses to declared incidents according to predefined procedures.
Perform root cause analysis on incidents to determine underlying causes.
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
Test the organizational incident response capability.
Use knowledge of attacker tactics, techniques, and procedures in incident response planning and execution.
Establish and maintain a security operations center capability that facilitates a 24/7 response capability.
Use a combination of manual and automated, real-time responses to anomalous activities that match incident patterns.
In response to cyber incidents, utilize forensic data gathering across impacted systems, ensuring the secure transfer and protection of forensic data.
Establish and maintain a cyber incident response team that can investigate an issue physically or virtually at any location within 24 hours.
Perform unannounced operational exercises to demonstrate technical and procedural responses.
Perform maintenance on organizational systems.
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
Supervise the maintenance activities of personnel without required access authorization.
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
Document the CMMC practices to implement the [DOMAIN NAME] policy.
Establish a policy that includes [DOMAIN NAME].
Establish, maintain, and resource a plan that includes [DOMAIN NAME].
Review and measure [DOMAIN NAME] activities for effectiveness.
Standardize and optimize a documented approach for [DOMAIN NAME] across all applicable organizational units.
Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.
Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
Limit access to CUI on system media to authorized users.
Control the use of removable media on system components.
Mark media with necessary CUI markings and distribution limitations.
Prohibit the use of portable storage devices when such devices have no identifiable owner.
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.
Escort visitors and monitor visitor activity.
Maintain audit logs of physical access.
Control and manage physical access devices.
Protect and monitor the physical facility and support infrastructure for organizational systems.
Enforce safeguarding measures for CUI at alternate work sites.
Screen individuals prior to authorizing access to organizational systems containing CUI.
Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
Regularly perform and test data backups.
Protect the confidentiality of backup CUI at storage locations.
Regularly perform complete, comprehensive, and resilient data backups as organizationally defined.
Ensure information processing facilities meet organizationally defined information security continuity, redundancy, and availability requirements.
Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI.
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
Remediate vulnerabilities in accordance with risk assessments.
Periodically perform risk assessments to identify and prioritize risks according to the defined risk categories, risk sources, and risk measurement criteria.
Develop and implement risk mitigation plans.
Manage non-vendorsupported products (e.g., end of life) separately and restrict as necessary to reduce risk.
Develop and update as required, a plan for managing supply chain risks associated with the IT supply chain.
Catalog and periodically update threat profiles and adversary TTPs
Employ threat intelligence to inform the development of the system and security architectures, selection of security solutions, monitoring, threat hunting, and response and recovery activities.
Perform scans for unauthorized ports available across perimeter network boundaries over the organization's Internet network boundaries and other organizationally defined boundaries.
Utilize an exception process for non-whitelisted software that includes mitigation techniques.
Analyze the effectiveness of security solutions at least annually to address anticipated risk to the system and the organization based on current and accumulated threat intelligence.
Receive and respond to cyber threat intelligence from information sharing forums and sources and communicate to stakeholders.
Establish and maintain a cyber threat hunting capability to search for indicators of compromise in organizational systems and detect, track, and disrupt threats that evade existing controls.
Design network and system security capabilities to leverage, integrate, and share indicators of compromise.
Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
Use encrypted sessions for the management of network devices.
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
Separate user functionality from system management functionality.
Prevent unauthorized and unintended information transfer via shared system resources.
Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling).
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
Establish and manage cryptographic keys for cryptography employed in organizational systems.
Control and monitor the use of mobile code.
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
Protect the authenticity of communications sessions.
Protect the confidentiality of CUI at rest.
Implement Domain Name System (DNS) filtering services.
Implement a policy restricting the publication of CUI on externally owned, publicly accessible websites (e.g., forums, LinkedIn, Facebook, Twitter).
Employ physical and logical isolation techniques in the system and security architecture and/or where deemed appropriate by the organization.
Utilize threat intelligence to proactively block DNS requests from reaching malicious domains.
Employ mechanisms to analyze executable code and scripts (e.g., sandbox) traversing Internet network boundaries or other organizationally defined boundaries.
Isolate administration of organizationally defined high value critical network infrastructure components and servers.
Utilize a URL categorization service and implement techniques to enforce URL filtering of websites that are not approved by the organization.
Configure monitoring systems to record packets passing through the organization's Internet network boundaries and other organizationally defined boundaries.
Employ organizationally defined and tailored boundary protections in addition to commercially available solutions.
Enforce port and protocol compliance.
Identify, report, and correct information and information system flaws in a timely manner.
Provide protection from malicious code at appropriate locations within organizational information systems.
Update malicious code protection mechanisms when new releases are available.
Perform periodic scans of the information system and realtime scans of files from external sources as files are downloaded, opened, or executed.
Monitor system security alerts and advisories and take action in response.
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
Identify unauthorized use of organizational systems.
Employ spam protection mechanisms at information system access entry and exit points.
Implement email forgery protections.
Utilize sandboxing to detect or block potentially malicious email.
Use threat indicator information relevant to the information and systems being protected and effective mitigations obtained from external organizations to inform intrusion detection and threat hunting.
Analyze system behavior to detect and mitigate execution of normal system commands and scripts that indicate malicious actions.
Monitor individuals and system components on an ongoing basis for anomalous or suspicious behavior.
Criminal Justice Information Services (CJIS) Security Policy 
0 / 82 selected   Deselect All Select All
Revert       Remove
Auditing and Accountability
Information Handling
Outsourcing Standards for Non-Channelers
Monitoring, Review, and Delivery of Services
Managing Changes to Service Providers
Information Flow Enforcement
Boundary Protection
Encryption for CJI in Transit
Encryption for CJI at Rest
Intrusion Detection Tools and Techniques
Cloud Computing
Patch Management
Malicious Code Protection
Spam and Spyware Protection
Security Alerts and Advisories
Audits by the CSA
Personnel Termination
802.11 Wireless Protocols
Cellular Devices
Cellular Service Abroad
Mobile Hotspots
Mobile Device Management (MDM)
Wireless Device Risk Mitigations
System Integrity
Patching/Updates (Mobile)
Malicious Code Protection (Mobile)
Personal Firewall (Mobile)
Incident Response (Mobile)
Access Control
Local Device Authentication
Advanced Authentication
Compensating Controls
Device Certificates
Level One Security Awareness Training
Level Two Security Awareness Training
Level Three Security Awareness Training
Level Four Security Awareness Training
Reporting Security Events
FBI CJIS Division Responsibilities
CSA ISO Responsibilities
Management of Security Incidents
Incident Handling
Collection of Evidence
Incident Response Training
Incident Monitoring
Auditable Events and Content (Information Systems)
Audit Monitoring, Analysis, and Reporting
Time Stamps
Audit Record Retention
Logging NCIC and III Transactions
Account Management
Access Enforcement
Least Privilege
System Access Control
Access Control Criteria
Access Control Mechanisms
Unsuccessful Login Attempts
Session Lock
Remote Access
Personally Owned Information Systems
Publicly Accessible Computers
Identification Policy and Procedures
Authentication Policy and Procedures
Advanced Authentication
Advanced Authentication Policy and Rationale
Identifier Management
Authenticator Management
Access Restrictions for Changes
Least Functionality
Network Diagram
Security of Configuration Documentation
Media Storage and Access
Media Transport
Digital Media during Transport
Digital Media Sanitization and Disposal
Cyber Essentials v2.2 
0 / 56 selected   Deselect All Select All
Revert       Remove
Please list the quantities of laptops, desktops and virtual desktops within the scope of this assessment. You must include model and operating system version for all devices. For Windows devices the Edition and Feature version are also required. All devices that are connecting to cloud services must be included.
Please list the quantity of thin clients within scope of this assessment. Please include make, model and operating systems.
Please list the quantities of servers, virtual servers and virtual server hosts (hypervisor). You must include the operating system.
Please list the quantities of tablets and mobile devices within the scope of this assessment. You must include model and operating system versions for all devices.
Please provide a list of network equipment that will be in scope for this assessment (including firewalls and routers). You must include make and model of each device listed.
Please list all cloud services that are provided by a third party and used by your organisation.
Do you have firewalls at the boundaries between your organisation’s internal networks, laptops, desktops, servers and the internet?
When corporate or user-owned devices (BYOD) are not connected to the organisation’s internal network, how are the firewall controls applied?
If yes, is the access to the settings protected by either multi-factor authentication or by only allowing trusted IP addresses combined with managed authentication to access the settings? Please explain which option is used.
Do you have software firewalls enabled on all of your computers, laptops and servers?
Is the new firewall password configured to meet the password-based authentication requirements? Please select the option being used: A. multi-factor authentication, with a minimum password length of 8 characters and no maximum length B. Automatic blocking of common passwords, with a minimum password length of 8 characters and no maximum length C. A password with a minimum length of 12 characters and no maximum length
Do you have any services enabled that can be accessed externally through your internet router, hardware firewall or software firewall?
Do you have a documented business case for all of these services?
Have you configured your boundary firewalls so that they block all other services from being advertised to the internet?
Are your boundary firewalls configured to allow access to their configuration settings over the internet?
Where you are able to do so, have you removed or disabled all the software that you do not use on your laptops, desktop computers, thin clients, servers, tablets, mobile phones and cloud services? Describe how you achieve this.
When a device requires a user to be present, do you set a locking mechanism on your devices to access the software and services installed?
Which method do you use to unlock the devices and what brute force protection is in place?
Have you ensured that all your laptops, computers, servers, tablets, mobile devices and cloud services only contain necessary user accounts that are regularly used in the course of your business?
Have you changed the default password for all user and administrator accounts on all your desktop computers, laptops, thin clients, servers, tablets and mobile phones that follow the Password-based authentication requirements of Cyber Essentials?
Do you run external services that provides access to data (that shouldn't be made public) to users across the internet?
If yes, which option of password-based authentication do you use? A. multi-factor authentication, with a minimum password length of 8 characters and no maximum length. B. Automatic blocking of common passwords, with a minimum password length of 8 characters and no maximum length. C. A password with a minimum length of 12 characters and no maximum length.
Is "auto-run" or "auto-play" disabled on all of your systems?
Are all operating systems and firmware on your devices supported by a vendor that produces regular security updates?
Is all software on your devices supported by a supplier that produces regular fixes for any security problems?
Please list your internet browser/s
Please list your malware protection
Please list your email applications installed on end user devices and servers.
Please list all office applications that are used to create organisational data.
Is all software licensed in accordance with the publisher’s recommendations?
Are all high-risk or critical security updates for operating systems and firmware installed within 14 days of release?
Are all updates applied for operating systems by enabling auto updates ?
Where auto updates are not being used, how do you ensure all high-risk or critical security updates of all operating systems and firmware are applied within 14 days of release?
Are all high-risk or critical security updates for applications (including any associated files and any plugins such as Java, Adobe Reader and .Net.) installed within 14 days of release?
Are all updates applied for applications by enabling auto updates?
Where auto updates are not being used, how do you ensure all high-risk or critical security updates of all applications are applied within 14 days of release?
Have you removed any applications on your devices that are no longer supported and no longer receive regular fixes for security problems?
Where unsupported software is in use, have those devices been moved to a segregated sub-set and internet access removed and how do you achieve this?
Are users only provided with user accounts after a process has been followed to approve their creation? Describe the process.
Please explain how you encourage people to use unique and strong passwords.
Have you enabled multi-factor authentication (MFA) on all of your cloud services?
Has MFA been applied to all administrators of your cloud services?
Can you only access laptops, computers and servers in your organisation (and the applications they contain) by entering a unique user name and password?
How do you ensure you have deleted, or disabled, any accounts for staff who are no longer with your organisation?
Do you ensure that staff only have the privileges that they need to do their current job? How do you do this?
Do you have a formal process for giving someone access to systems at an “administrator” level? Describe the process.
How do you ensure that administrator accounts are used only to carry out administrative tasks (such as installing software or making configuration changes)?
How do you ensure that administrator accounts are not used for accessing email or web browsing?
Do you formally track which users have administrator accounts in your organisation?
Do you review who should have administrative access on a regular basis?
Are all of your desktop computers, laptops, tablets and mobile phones protected from malware by either: A - having anti-malware software installed and/or: B - limiting installation of applications to an approved set (i.e. using an App Store and a list of approved applications) and/or: C - application sandboxing (i.e. by using a virtual machine)?
(A) Where you have anti-malware software installed, is it set to update daily and scan files automatically upon access?
(A) Where you have anti-malware software installed, is it set to scan web pages you visit and warn you about accessing malicious websites?
(B) Where you use an app-store or application signing, are users restricted from installing unsigned applications?
(B) Where you use an app-store or application signing, do you ensure that users only install applications that have been approved by your organisation and do you document this list of approved applications?
(C) Where you use application sandboxing, do you ensure that applications within the sandbox are unable to access data stores, sensitive peripherals and your local network? Describe how you achieve this.
Federal Financial Institutions Examination Council (FFIEC-CAT) 
0 / 95 selected   Deselect All Select All
Revert       Remove
An inventory of organizational assets (e.g., hardware, software, data, and systems hosted externally) is maintained.
Organizational assets (e.g., hardware, systems, data, and applications) are prioritized for protection based on the data classification and business value.
A change management process is in place to request and approve changes to systems configurations, hardware, software, applications, and security tools.
The institution has an information security strategy that integrates technology, policies, procedures, and training to mitigate risk.
The institution has policies commensurate with its risk and complexity that address the concepts of information technology risk management.
The institution has policies commensurate with its risk and complexity that address the concepts of external dependency or third-party management.
The institution has policies commensurate with its risk and complexity that address the concepts of incident response and resilience.
Information security roles and responsibilities have been identified.
Independent audit or review evaluates policies, procedures, and controls across the institution for significant risks and control issues associated with the institution's operations, including risks in new products, emerging technologies, and information systems.
The independent audit function validates controls related to the storage or transmission of confidential data.
Logging practices are independently reviewed periodically to ensure appropriate log management (e.g., access controls, retention, and maintenance).
An information security and business continuity risk management function(s) exists within the institution.
Annual information security training is provided.
Annual information security training includes incident response, current cyber threats (e.g., phishing, spear phishing, social engineering, and mobile security), and emerging issues.
Situational awareness materials are made available to employees when prompted by highly visible cyber events or by regulatory alerts.
Customer awareness materials are readily available (e.g., DHS’ Cybersecurity Awareness Month materials).
Contact information for law enforcement and the regulator(s) is maintained and updated regularly.
Information about threats is shared with law enforcement and regulators when required or prompted.
Audit log records and other security event logs are reviewed and retained in a secure manner.
Computer event logs are used for investigations once an event has occurred.
Threat information is used to enhance internal risk management and controls.
A patch management program is implemented and ensures that software and firmware patches are applied in a timely manner.
Patches are tested before being applied to systems and/or software.
Patch management reports are reviewed and reflect missing security patches.
Issues identified in assessments are prioritized and resolved based on criticality and within the time frames established in the response to the assessment report.
The institution is able to detect anomalous activities through monitoring across the environment.
Logs of physical and/or logical access are reviewed following events.
Access to critical systems by third parties is monitored for unauthorized or unusual activity.
Elevated privileges are monitored.
A normal network activity baseline is established.
Mechanisms (e.g., antivirus alerts, log event alerts) are in place to alert management to potential attacks.
Processes are in place to monitor for the presence of unauthorized users, devices, connections, and software.
Independent testing (including penetration testing and vulnerability scanning) is conducted according to the risk assessment for external-facing systems and the internal network.
Antivirus and anti-malware tools are used to detect attacks.
E-mail protection mechanisms are used to filter for common cyber threats (e.g., attached malware or malicious links).
Employee access is granted to systems and confidential data based on job responsibilities and the principles of least privilege.
Production and non-production environments are segregated to prevent unauthorized access or changes to information assets. (*N/A if no production environment exists at the institution or the institution’s third party.)
All passwords are encrypted in storage and in transit.
Confidential data are encrypted when transmitted across public or untrusted networks (e.g., Internet).
Mobile devices (e.g., laptops, tablets, and removable media) are encrypted if used to store confidential data. (*N/A if mobile devices are not used.)
Remote access to critical systems by employees, contractors, and third parties uses encrypted connections and multifactor authentication.
Administrative, physical, or technical controls are in place to prevent users without administrative responsibilities from installing unauthorized software.
Data is disposed of or destroyed according to documented requirements and within expected time frames.
Employee access to systems and confidential data provides for separation of duties.
Elevated privileges (e.g., administrator privileges) are limited and tightly controlled (e.g., assigned to individuals, not shared, and require stronger password controls).
User access reviews are performed periodically for all systems and applications based on the risk to the application or system.
Changes to physical and logical user access, including those that result from voluntary and involuntary terminations, are submitted to and approved by appropriate personnel.
Identification and authentication are required and managed for access to systems, applications, and hardware.
Access controls include password complexity and limits to password attempts and reuse.
All default passwords and unnecessary default accounts are changed before system implementation.
Customer access to Internet-based products or services requires authentication controls (e.g., layered controls, multifactor) that are commensurate with the risk.
Controls are in place to restrict the use of removable media to authorized personnel.
Network perimeter defense tools (e.g., border router and firewall) are used.
Wireless network environments require security settings with strong encryption for authentication and transmission. (*N/A if there are no wireless networks.)
Systems that are accessed from the Internet or by external parties are protected by firewalls or other similar devices.
All ports are monitored.
Up to date antivirus and anti-malware tools are used.
Systems configurations (for servers, desktops, routers, etc.) follow industry standards and are enforced.
Ports, functions, protocols and services are prohibited if no longer needed for business purposes.
Access to make changes to systems configurations (including virtual machines and hypervisors) is controlled and monitored.
System sessions are locked after a pre-defined period of inactivity and are terminated after pre-defined conditions are met.
Developers working for the institution follow secure program coding practices, as part of a system development life cycle (SDLC), that meet industry standards.
The security controls of internally developed software are periodically reviewed and tested. (*N/A if there is no software development.)
The security controls in internally developed software code are independently reviewed before migrating the code to production. (*N/A if there is no software development.)
The institution ensures that third-party connections are authorized.
A network diagram is in place and identifies all external connections.
Data flow diagrams are in place and document information flow to external parties.
Formal contracts that address relevant security and privacy requirements are in place for all third parties that process, store, or transmit confidential data or provide critical services.
Contracts acknowledge that the third party is responsible for the security of the institution’s confidential data that it possesses, stores, processes, or transmits.
Contracts stipulate that the third-party security controls are regularly reviewed and validated by an independent party.
Contracts identify the recourse available to the institution should the third party fail to meet defined security requirements.
Contracts establish responsibilities for responding to security incidents.
Contracts specify the security requirements for the return or destruction of data upon contract termination.
Risk-based due diligence is performed on prospective third parties before contracts are signed, including reviews of their background, reputation, financial condition, stability, and security controls.
A list of third-party service providers is maintained.
A risk assessment is conducted to identify criticality of service providers.
The third-party risk assessment is updated regularly.
Audits, assessments, and operational performance reports are obtained and reviewed regularly validating security controls for critical third parties.
Ongoing monitoring practices include reviewing critical third-parties’ resilience plans.
Alert parameters are set for detecting information security incidents that prompt mitigating actions.
System performance reports contain information that can be used as a risk indicator to detect information security incidents.
Tools and processes are in place to detect, alert, and trigger the incident response program.
Appropriate steps are taken to contain and control an incident to prevent further unauthorized access to or use of customer information.
A process exists to contact personnel who are responsible for analyzing and responding to an incident.
Procedures exist to notify customers, regulators, and law enforcement as required or necessary when the institution becomes aware of an incident involving the unauthorized access to or use of sensitive customer information.
Incidents are classified, logged, and tracked.
The institution has documented how it will react and respond to cyber incidents.
Communication channels exist to provide employees a means for reporting information security events in a timely manner.
Roles and responsibilities for incident response team members are defined.
The response team includes individuals with a wide range of backgrounds and expertise, from many different areas within the institution (e.g., management, legal, public relations, as well as information technology).
A formal backup and recovery plan exists for all critical business lines.
The institution plans to use business continuity, disaster recovery, and data backup programs to recover operations following an incident.
Scenarios are used to improve incident detection and response.
Business continuity testing involves collaboration with critical third parties.
Systems, applications, and data recovery is tested at least annually.
0 / 42 selected   Deselect All Select All
Revert       Remove
Contingency operations
Security management process
Risk analysis
Risk management
Information system activity review
Assigned security responsibility
Workforce security
Authorization and/or supervision
Workforce clearance procedure
Termination procedures
Information access management
Isolating health care clearinghouse functions
Access establishment and modification
Security awareness and training
Security reminders
Protection from malicious software
Log-in monitoring
Password management
Security incident procedures
Response and Reporting
Contingency plan
Data backup plan
Disaster recovery plan
Testing and revision procedures
Business associate contracts and other arrangements (1)
Business associate contracts and other arrangements (2)
Implementation specifications: Written contract or other arrangement
Device and media controls
Data backup and storage
Access control
Unique user identification
Automatic logoff
Encryption and decryption
Audit controls
Mechanism to authenticate electronic protected health information
Transmission security
Integrity controls
0 / 18 selected   Deselect All Select All
Revert       Remove
Managed I&T Management Framework
Managed Enterprise Architecture
Managed Service Agreements
Managed Vendors
Managed Risk
Managed Security
Managed Data
Managed Programs
Managed IT Changes
Managed Knowledge
Managed Assets
Managed Configuration
Managed Projects
Managed Problems
Managed Continuity
Managed Security Services
Managed Business Process Controls
Ensured Risk Optimization
MITRE Enterprise ATT&CK v8.2 
0 / 383 selected   Deselect All Select All
Revert       Remove
Data Obfuscation
Junk Data
Protocol Impersonation
OS Credential Dumping
LSASS Memory
Security Account Manager
LSA Secrets
Cached Domain Credentials
Proc Filesystem
/etc/passwd and /etc/shadow
Fallback Channels
Exfiltration Over Other Network Medium
Exfiltration Over Bluetooth
Traffic Duplication
Remote Services
Remote Desktop Protocol
SMB/Windows Admin Shares
Distributed Component Object Model
Windows Remote Management
Obfuscated Files or Information
Software Packing
Scheduled Transfer
Data Transfer Size Limits
Invalid Code Signature
Rename System Utilities
Match Legitimate Name or Location
Boot or Logon Initialization Scripts
Logon Script (Windows)
Logon Script (Mac)
Network Logon Script
Startup Items
Network Sniffing
Exfiltration Over C2 Channel
Network Service Scanning
Windows Management Instrumentation
Exfiltration Over Alternative Protocol
Exfiltration Over Symmetric Encrypted Non-C2 Protocol
Exfiltration Over Asymmetric Encrypted Non-C2 Protocol
Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol