Citations: CIS Controls® V7.1

The processes and tools used to prevent data exfiltration, mitigate the effects of exfiltrated data, and ensure the privacy and integrity of sensitive information.

Minimize the attack surface and the opportunities for attackers to manipulate human behavior though their interaction with web browsers and email systems.

Manage (track/control/correct) the ongoing operational use of ports, protocols, and services on networked devices in order to minimize windows of vulnerability available to attackers.

The processes and tools used to track/control/prevent/correct secure access to critical assets (e.g., information, resources, systems) according to the formal determination of which persons, computers, and applications have a need and right to access these critical assets based on an approved classi

The processes and tools used to track/control/prevent/correct the use, assignment, and configuration of administrative privileges on computers, networks, and applications.

Utilize an active discovery tool to identify devices connected to the organization's network and update the hardware asset inventory.

Block all e-mail attachments entering the organization's e-mail gateway if the file types are unnecessary for the organization's business.

To lower the chance of spoofed or modified emails from valid domains, implement Domain-based Message Authentication, Reporting and Conformance (DMARC) policy and verification, starting by implementing the Sender Policy Framework (SPF) and the DomainKeys Identified Mail(DKIM) standards.

Use sandboxing to analyze and block inbound email attachments with malicious behavior.

Place application firewalls in front of any critical servers to verify and validate the traffic going to the server. Any unauthorized traffic should be blocked and logged.

Ensure that unauthorized assets are either removed from the network, quarantined, or the inventory is updated in a timely manner.

Ensure that the hardware asset inventory records the network address, hardware address, machine name, data asset owner, and department for each asset and whether the hardware asset has been approved to connect to the network.

Maintain an accurate and up-to-date inventory of all technology assets with the potential to store or process information. This inventory shall include all hardware assets, whether connected to the organization's network or not.

The processes and tools used to properly back up critical information with a proven methodology for timely recovery of it.

Ensure that all backups have at least one backup destination that is not continuously addressable through operating system calls.

Ensure that backups are properly protected via physical security or encryption when they are stored, as well as when they are moved across the network. This includes remote backups and cloud services.

Ensure that all system data is automatically backed up on regular basis.

Ensure that each of the organization's key systems are backed up as a complete system, through processes such as imaging, to enable the quick recovery of an entire system.

Test data integrity on backup media on a regular basis by performing a data restoration process to ensure that the backup is properly working.

Detect/prevent/correct the flow of information transferring networks of different trust levels with a focus on security-damaging data.

Continuously acquire, assess, and take action on new information in order to identify vulnerabilities, remediate, and minimize the window of opportunity for attackers.

This is a great passive way to monitor for malware in an environment. these sensors can log all of these queries without having to pull them off of the endpoint. Looking for new DNS queries and those that look to be computer-generated will be quick wins in terms of hunting out malware infections.

Use DNS filtering services to help block access to known malicious domains.

Maintain an inventory of all sensitive information stored, processed, or transmitted by the organization's technology systems, including those located onsite or at a remote service provider.

Remove sensitive data or systems not regularly accessed by the organization from the network. These systems shall only be used as stand alone systems (disconnected from the network) by the business unit needing to occasionally use the system or completely virtualized and powered off until needed.

Utilize an active discovery tool to identify all sensitive information stored, processed, or transmitted by the organization's technology systems, including those located onsite or at a remote service provider and update the organization's sensitive information inventory.

Manage the network infrastructure across network connections that are separated from the business use of that network, relying on separate VLANs or, preferably, on entirely different physical connectivity for management sessions for network devices.

Ensure network engineers use a dedicated machine for all administrative tasks or tasks requiring elevated access. This machine shall be segmented from the organization's primary network and not be allowed Internet access. This machine shall not be used for reading e-mail, composing documents, or sur

Ensure administrators use a dedicated machine for all administrative tasks or tasks requiring administrative access. This machine will be segmented from the organization's primary network and not be allowed Internet access. This machine will not be used for reading e-mail, composing documents, or br

The important aspect of this requirement is getting the logs off of the endpoint so a malware infection doesn’t clear them out.

Most AVs have this capability turned on by default, but it’s still important to verify that it’s actually still enabled. Malware coming in via a USB stick is a viable attack vector for nearly every organization.

Provide the training to employees so they are aware of the risks of data on USB drives. Then provide them with the tools to secure your organization’s critical data.

The AV is only as good as it’s signatures. While pure signature-based detection is no longer viable, even anomaly-based engines need to be updated on a regular basis. Ensure that the updates are rolled out automatically and use tools to verify that the signatures are actually up-to-date

Install AV and run updates regularly. This has been ingrained in IT professionals for decades. The only key aspects is to make sure the AV solution meets the needs of your organization in terms of capabilities.

Configure systems not to write data to external removable media, if there is no business need for supporting such devices.

If USB storage devices are required, enterprise software should be used that can configure systems to allow the use of specific devices. An inventory of such devices should be maintained.

Any enterprise class AV software will have this capability. By having a centrally managed AV, you can easily enable individual requirements.

Encrypt all sensitive information at rest using a tool that requires a secondary authentication mechanism not integrated into the operating system, in order to access the information.

Use an automated tool, such as host-based Data Loss Prevention, to enforce access controls to data even when data is copied off a system.

Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed.

Actively manage the life cycle of system and application accounts - their creation, use, dormancy, deletion - in order to minimize opportunities for attackers to leverage them.

Configure access for all accounts through as few centralized points of authentication as possible, including network, security, and cloud systems.

Disable any account that cannot be associated with a business process or business owner.

Automatically disable dormant accounts after a set period of inactivity.

Ensure that all account usernames and authentication credentials are transmitted across networks using encrypted channels.

Encrypt or hash with a salt all authentication credentials when stored.

Ensure that all accounts have an expiration date that is monitored and enforced.

Establish and follow an automated process for revoking system access by disabling accounts immediately upon termination or change of responsibilities of an employee or contractor . Disabling these accounts, instead of deleting accounts, allows preservation of audit trails.

Automatically lock workstation sessions after a standard period of inactivity.

Maintain an inventory of all accounts organized by authentication system.

Maintain an inventory of each of the organization's authentication systems, including those located onsite or at a remote service provider.

Assign job titles and duties for handling computer and network incidents to specific individuals and ensure tracking and documentation throughout the incident through resolution.

Plan and conduct routine incident response exercises and scenarios for the workforce involved in the incident response to maintain awareness and comfort in responding to real world threats. Exercises should test communication channels, decision making, and incident responders technical capabilities

Create incident scoring and prioritization schema based on known or potential impact to your organization. Utilize score to define frequency of status updates and escalation procedures.

Designate management personnel, as well as backups, who will support the incident handling process by acting in key decision-making roles.

Devise organization-wide standards for the time required for system administrators and other workforce members to report anomalous events to the incident handling team, the mechanisms for such reporting, and the kind of information that should be included in the incident notification.

Ensure that there are written incident response plans that defines roles of personnel as well as phases of incident handling/management.

Protect the organization's information, as well as its reputation, by developing and implementing an incident response infrastructure (e.g., plans, defined roles, training, communications, management oversight) for quickly discovering an attack and then effectively containing the damage, eradicating

Assemble and maintain information on third-party contact information to be used to report a security incident, such as Law Enforcement, relevant government departments, vendors, and ISAC partners.

Publish information for all workforce members, regarding reporting computer anomalies and incidents to the incident handling team. Such information should be included in routine employee awareness activities.

Ensure that local logging has been enabled on all systems and networking devices.

Alert when users deviate from normal login behavior, such as time-of-day, workstation location and duration.

Ensure that appropriate logs are being aggregated to a central log management system for analysis and review.

Deploy Security Information and Event Management (SIEM) or log analytic tool for log correlation and analysis.

On high interaction systems, this can be quite noisy. From a forensics standpoint, it will be quite valuable.

Enable system logging to include detailed information such as a event source, date, user, timestamp, source addresses, destination addresses, and other useful elements.

Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring).

Ensure that all systems that store logs have adequate storage space for the logs generated.

Log all URL requests from each of the organization's systems, whether onsite or a mobile device, in order to identify potentially malicious activity and assist incident handlers with identifying potentially compromised systems.

Configure systems to issue a log entry and alert when an account is added to or removed from any group assigned administrative privileges.

Configure systems to issue a log entry and alert on unsuccessful logins to an administrative account.

Monitor attempts to access deactivated accounts through audit logging.

On a regular basis, review logs to identify anomalies or abnormal events.

On a regular basis, tune your SIEM system to better identify actionable events and decrease event noise.

Use Dynamic Host Configuration Protocol (DHCP) logging on all DHCP servers or IP address management tools to update the organization's hardware asset inventory.

Collect, manage, and analyze audit logs of events that could help detect, understand, or recover from an attack.

Manage all network devices using multi-factor authentication and encrypted sessions.

Require all remote login access to the organization's network to encrypt data in transit and use multi-factor authentication.

Require multi-factor authentication for all user accounts, on all systems, whether managed onsite or by a third-party provider.

Use multi-factor authentication and encrypted channels for all administrative account access.

Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals.

Monitor all traffic leaving the organization and detect any unauthorized use of encryption.

Deploy network-based Intrusion Detection Systems (IDS) sensors to look for unusual attack mechanisms and detect compromise of these systems at each of the organization's network boundaries.

Deploy network-based Intrusion Prevention Systems (IPS) to block malicious network traffic at each of the organization's network boundaries.

Create a separate wireless network for personal or untrusted devices. Enterprise access from this network should be treated as untrusted and filtered and audited accordingly.

Enable the collection of NetFlow and logging data on all network boundary devices.

All configuration rules that allow traffic to flow through network devices should be documented in a configuration management system with a specific business reason for each rule, a specific individual’s name responsible for that business need, and an expected duration of the need.

Install the latest stable version of any security-related updates on all network devices.

Leverage the Advanced Encryption Standard (AES) to encrypt wireless data in transit.

Maintain standard, documented security configuration standards for all authorized network devices.

Maintain an inventory of authorized wireless access points connected to the wired network.

Establish, implement, and actively manage (track, report on, correct) the security configuration of network infrastructure devices using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings.

Compare all network device configuration against approved security configurations defined for each network device in use and alert when any deviations are discovered.

Ensure that wireless networks use authentication protocols such as Extensible Authentication Protocol-Transport Layer Security (EAP/TLS), that requires mutual, multi-factor authentication.

The processes and tools used to track/control/prevent/correct the security use of wireless local area networks (WLANs), access points, and wireless client systems.

Decrypt all encrypted network traffic at the boundary proxy prior to analyzing the content. However, the organization may use whitelists of allowed sites that can be accessed through the proxy without decrypting the traffic.

Deny communication over unauthorized TCP or UDP ports or application traffic to ensure that only authorized protocols are allowed to cross the network boundary in or out of the network at each of the organization's network boundaries.

Deny communications with known malicious or unused Internet IP addresses and limit access only to trusted and necessary IP address ranges at each of the organization's network boundaries,.

Ensure that all network traffic to or from the Internet passes through an authenticated application layer proxy that is configured to filter unauthorized connections.

Disable all workstation to workstation communication to limit an attacker's ability to move laterally and compromise neighboring systems, through technologies such as Private VLANs or microsegmentation.

Enable firewall filtering between VLANs to ensure that only authorized systems are able to communicate with other systems necessary to fulfill their specific responsibilities.

Maintain an up-to-date inventory of all of the organization's network boundaries.

Only allow access to authorized cloud storage or email providers.

Physically or logically segregated systems should be used to isolate and run software that is required for business operations but incur higher risk for the organization.

Segment the network based on the label or classification level of the information stored on the servers, locate all sensitive information on separated Virtual Local Area Networks (VLANs).

Utilize port level access control, following 802.1x standards, to control which devices can authenticate to the network. The authentication system shall be tied into the hardware asset inventory data to ensure only authorized devices can connect to the network.

Configure monitoring systems to record network packets passing through the boundary at each of the organization's network boundaries.

Use at least three synchronized time sources from which all servers and network devices retrieve time information on a regular basis so that timestamps in logs are consistent.

Enforce network-based URL filters that limit a system's ability to connect to websites not approved by the organization. This filtering shall be enforced for each of the organization's systems, whether they are physically at an organization's facilities or not.

Subscribe to URL categorization services to ensure that they are up-to-date with the most recent website category definitions available. Uncategorized sites shall be blocked by default.

Utilize a passive discovery tool to identify devices connected to the organization's network and automatically update the organization's hardware asset inventory.

Deploy automated software update tools in order to ensure that the operating systems are running the most recent security updates provided by the software vendor.

Deploy automated software update tools in order to ensure that third-party software on all systems is running the most recent security updates provided by the software vendor.

Conduct regular external and internal penetration tests to identify vulnerabilities and attack vectors that can be used to exploit enterprise systems successfully.

Any user or system accounts used to perform penetration testing should be controlled and monitored to make sure they are only being used for legitimate purposes, and are removed or restored to normal function after testing is over.

Create a test bed that mimics a production environment for specific penetration tests and Red Team attacks against elements that are not typically tested in production, such as attacks against supervisory control and data acquisition and other control systems.

Wherever possible, ensure that Red Teams results are documented using open, machine-readable standards (e.g., SCAP). Devise a scoring method for determining the results of Red Team exercises so that results can be compared over time.

Establish a program for penetration tests that includes a full scope of blended attacks, such as wireless, client-based, and web application attacks.

Include tests for the presence of unprotected system information and artifacts that would be useful to attackers, including network diagrams, configuration files, older penetration test reports, e-mails or documents containing passwords or other information critical to system operation.

Test the overall strength of an organization's defense (the technology, the processes, and the people) by simulating the objectives and actions of an attacker.

Perform periodic Red Team exercises to test organizational readiness to identify and stop attacks or to respond quickly and effectively.

Use vulnerability scanning and penetration testing tools in concert. The results of vulnerability scanning assessments should be used as a starting point to guide and focus penetration testing efforts.

Before deploying any new asset, change all default passwords to have values consistent with administrative level accounts.

Ensure that all users with administrative account access use a dedicated or secondary account for elevated activities. This account should only be used for administrative activities and not internet browsing, email, or similar activities.

Use automated tools to inventory all administrative accounts, including domain and local accounts, to ensure that only authorized individuals have elevated privileges.

Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system.

Use client certificates to authenticate hardware assets connecting to the organization's trusted network.

Associate active ports, services and protocols to the hardware assets in the asset inventory.

Regularly compare the results from back-to-back vulnerability scans to verify that vulnerabilities have been remediated in a timely manner.

Configure network vulnerability scanning tools to detect and alert on unauthorized wireless access points connected to the wired network.

Ensure that only network ports, protocols, and services listening on a system with validated business needs, are running on each system.

Utilize a Security Content Automation Protocol (SCAP) compliant configuration monitoring system to verify all security configuration elements, catalog approved exceptions, and alert when unauthorized changes occur.

Perform authenticated vulnerability scanning with agents running locally on each system or with remote scanners that are configured with elevated rights on the system being tested.

Perform automated port scans on a regular basis against all systems and alert if unauthorized ports are detected on a system.

Use a dedicated account for authenticated vulnerability scans, which should not be used for any other administrative activities and should be tied to specific machines at specific IP addresses.

Utilize an up-to-date SCAP-compliant vulnerability scanning tool to automatically scan all systems on the network on a weekly or more frequent basis to identify all potential vulnerabilities on the organization's systems.

Utilize a risk-rating process to prioritize the remediation of discovered vulnerabilities.

Manage the security life cycle of all in-house developed and acquired software in order to prevent, detect, and correct security weaknesses.

For in-house developed software, ensure that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ranges or formats.

Establish secure coding practices appropriate to the programming language and development environment being used.

Only use up-to-date and trusted third-party components for the software developed by the organization.

Maintain separate environments for production and nonproduction systems. Developers should not have unmonitored access to production environments.

Use only standardized and extensively reviewed encryption algorithms.

Verify that the version of all software acquired from outside your organization is still supported by the developer or appropriately hardened based on developer security recommendations.

Establish, implement, and actively manage (track, report on, correct) the security configuration of mobile devices, laptops, servers, and workstations using a rigorous configuration management and change control process in order to prevent attackers from exploiting vulnerable services and settings.

Ensure that unauthorized software is either removed or the inventory is updated in a timely manner.

Ensure that only software applications or operating systems currently supported by the software's vendor are added to the organization's authorized software inventory. Unsupported software should be tagged as unsupported in the inventory system.

The software inventory system should be tied into the hardware asset inventory so all devices and associated software are tracked from a single location.

Maintain an up-to-date list of all authorized software that is required in the enterprise for any business purpose on any business system.

The software inventory system should track the name, version, publisher, and install date for all software, including operating systems authorized by the organization.

Utilize software inventory tools throughout the organization to automate the documentation of all software on business systems.

Apply static and dynamic analysis tools to verify that secure coding practices are being adhered to for internally developed software.

Establish a process to accept and address reports of software vulnerabilities, including providing a means for external entities to contact your security group.

Uninstall or disable any unauthorized browser or email client plugins or add-on applications.

Ensure that only fully supported web browsers and email clients are allowed to execute in the organization, ideally only using the latest version of the browsers and email clients provided by the vendor.

The organization's application whitelisting software must ensure that only authorized software libraries (such as *.dll, *.ocx, *.so, etc) are allowed to load into a system process.

The organization's application whitelisting software must ensure that only authorized, digitally signed scripts (such as *.ps1, *.py, macros, etc) are allowed to run on a system.

Limit access to scripting tools (such as Microsoft PowerShell and Python) to only administrative or development users with the need to access those capabilities.

Utilize application whitelisting technology on all assets to ensure that only authorized software executes and all unauthorized software is blocked from executing on assets.

Maintain documented, standard security configuration standards for all authorized operating systems and software.

Maintain secure images or templates for all systems in the enterprise based on the organization's approved configuration standards. Any new system deployment or existing system that becomes compromised should be imaged using one of those images or templates.

Store the master images and templates on securely configured servers, validated with integrity monitoring tools, to ensure that only authorized changes to the images are possible.

For the same reason why you do not want to scan it, you also don’t want it to run when it’s mounted. This is a pretty quick setting to enable, and both CIS and DISA hardening guides have step-by-step instructions on disabling auto-run. Some SCM tools can quickly check every endpoint in your environm

Deploy system configuration management tools that will automatically enforce and redeploy configuration settings to systems at regularly scheduled intervals.

Disable peer-to-peer (adhoc) wireless network capabilities on wireless clients.

Disable wireless access on devices that do not have a business purpose for wireless access.

Disable wireless peripheral access of devices (such as Bluetooth and NFC), unless such access is required for a business purpose.

The DISA hardening guides provide step-by-step instructions on enabling these settings and so much more.

Encrypt all sensitive information in transit.

Ensure that only authorized scripting languages are able to run in all web browsers and email clients.

Configure wireless access on client machines that do have an essential wireless business purpose, to allow access only to authorized wireless networks and to restrict access to other wireless networks.

Scan all enterprise devices remotely logging into the organization's network prior to accessing the network to ensure that each of the organization's security policies has been enforced in the same manner as local network devices.

Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as

Perform regular scans from outside each trusted network boundary to detect any unauthorized connections which are accessible across the boundary.

For applications that rely on a database, use standard hardening configuration templates. All systems that are part of critical business processes should also be tested.

Deliver training to address the skills gap identified to positively impact workforce members' security behavior.

Ensure that all software development personnel receive training in writing secure code for their specific development environment and responsibilities.

Create a security awareness program for all workforce members to complete on a regular basis to ensure they understand and exhibit the necessary behaviors and skills to help ensure the security of the organization. The organization's security awareness program should be communicated in a continuous

For all functional roles in the organization (prioritizing those mission-critical to the business and its security), identify the specific knowledge, skills, and abilities needed to support defense of the enterprise; develop and execute an integrated plan to assess, identify gaps, and remediate thro

Perform a skills gap analysis to understand the skills and behaviors workforce members are not adhering to, using this information to build a baseline education roadmap.

Train employees to be able to identify the most common indicators of an incident and be able to report such an incident.

Train workforce members to be aware of causes for unintentional data exposures, such as losing their mobile devices or emailing the wrong person due to autocomplete in email.

Train the workforce on how to identify different forms of social engineering attacks, such as phishing, phone scams and impersonation calls.

Train workforce members on the importance of enabling and utilizing secure authentication.

Train workforce on how to identify and properly store, transfer, archive and destroy sensitive information.

Ensure that the organization's security awareness program is updated frequently (at least annually) to address new technologies, threats, standards and business requirements.

Actively manage (inventory, track, and correct) all hardware devices on the network so that only authorized devices are given access, and unauthorized and unmanaged devices are found and prevented from gaining access.

Actively manage (inventory, track, and correct) all software on the network so that only authorized software is installed and can execute, and that unauthorized and unmanaged software is found and prevented from installation or execution.

Protect web applications by deploying web application firewalls (WAFs) that inspect all traffic flowing to the web application for common web application attacks. For applications that are not web-based, specific application firewalls should be deployed if such tools are available for the given appl

Utilize approved whole disk encryption software to encrypt the hard drive of all mobile devices.

Use a wireless intrusion detection system (WIDS) to detect and alert on unauthorized wireless access points connected to the network.