Most linked-to categories

Showing below up to 50 results in range #801 to #850.

801. CIS - 13.5 - Protect - Devices - Manage Access Control for Remote Assets‏‎ (1 member)
802. CIS - 3.5 - Protect - Data - Securely Dispose of Data‏‎ (1 member)
803. Protecting Sensitive Sudent Information‏‎ (1 member)
804. Journalists-1.5‏‎ (1 member)
805. Political and Social-1.5‏‎ (1 member)
806. CIS - 17.9 - Recover - Establish and Maintain Security Incident Thresholds‏‎ (1 member)
807. CIS - 3.1 - Identify - Data - Establish and Maintain a Data Management Process‏‎ (1 member)
808. CIS - 10.3 - Protect - Devices - Disable Autorun and Autoplay for Removable Media‏‎ (1 member)
809. CIS - 14.5 - Protect - Train Workforce Members on Causes of Unintentional Data Exposure‏‎ (1 member)
810. CIS - 6.1 - Protect - Users - Establish an Access Granting Process‏‎ (1 member)
811. CIS - 4.1 - Respond - Devices - Enforce Automatic Device Lockout on Portable End-User Devices‏‎ (1 member)
812. CIS - 2.2 - Identify - Applications - Ensure Authorized Software is Currently Supported‏‎ (1 member)
813. CIS - 11.2 - Recover - Data - Perform Automated Backups‏‎ (1 member)
814. CIS - 16.14 - Protect - Applications - Conduct Threat Modeling‏‎ (1 member)
815. ID.RA-2: Cyber threat intelligence is received from information sharing forums and sources‏‎ (1 member)
816. ID.AM-4: External information systems are catalogued‏‎ (1 member)
817. DE.AE-4: Impact of events is determined‏‎ (1 member)
818. PR.IP-2: A System Development Life Cycle to manage systems is implemented‏‎ (1 member)
819. ID.GV-2: Cybersecurity roles and responsibilities are coordinated and aligned with internal roles and external partners‏‎ (1 member)
820. PR.AT-2: Privileged users understand their roles and responsibilities‏‎ (1 member)
821. PR.DS-7: The development and testing environment(s) are separate from the production environment‏‎ (1 member)
822. ID.SC-4: Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations.‏‎ (1 member)
823. RS.AN-4: Incidents are categorized consistent with response plans‏‎ (1 member)
824. PR.AT-4: Senior executives understand their roles and responsibilities‏‎ (1 member)
825. PR.MA-1: Maintenance and repair of organizational assets are performed and logged, with approved and controlled tools‏‎ (1 member)
826. DE.DP-4: Event detection information is communicated‏‎ (1 member)
827. NIST CSF v1.1‏‎ (1 member)
828. RS.IM-2: Response strategies are updated‏‎ (1 member)
829. RS.AN-5: Processes are established to receive, analyze and respond to vulnerabilities disclosed to the organization from internal and external sources (e.g. internal testing, security bulletins, or security researchers)‏‎ (1 member)
830. DE.AE-2: Detected events are analyzed to understand attack targets and methods‏‎ (1 member)
831. ID.BE-5: Resilience requirements to support delivery of critical services are established for all operating states (e.g. under duress or attack, during recovery, normal operations)‏‎ (1 member)
832. PR.IP-5: Policy and regulations regarding the physical operating environment for organizational assets are met‏‎ (1 member)
833. RC.RP-1: Recovery plan is executed during or after a cybersecurity incident‏‎ (1 member)
834. Recovery Planning (RC.RP)‏‎ (1 member)
835. Utilities‏‎ (1 member)
836. CIS - 8.4 - Protect - Network - Standardize Time Synchronization‏‎ (1 member)
837. GEN - Vulnerability Management‏‎ (1 member)
838. CIS - 8.12 - Detect - Data - Collect Service Provider Logs‏‎ (1 member)
839. Ethernet‏‎ (1 member)
840. What is a Private Key?‏‎ (1 member)
841. Business AI Chatbots‏‎ (1 member)
842. CIS - 6.2 - Protect - Users - Establish an Access Revoking Process‏‎ (1 member)
843. CIS - 2.1 - Identify - Applications - Establish and Maintain a Software Inventory‏‎ (1 member)
844. ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated‏‎ (1 member)
845. PR.IP-1: A baseline configuration of information technology or industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality)‏‎ (1 member)
846. ID.RM-3: The organization’s determination of risk tolerance is informed by its role in critical infrastructure and sector specific risk analysis‏‎ (1 member)
847. DE.AE-5: Incident alert thresholds are established‏‎ (1 member)
848. PR.DS-5: Protections against data leaks are implemented‏‎ (1 member)
849. CIS - 14.7 - Protect - Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates‏‎ (1 member)
850. RS.MI-2: Incidents are mitigated‏‎ (1 member)