WorkAxle Trust Center

Below is a list of all related controls for this domain. A status of green means compliant, yellow means partially compliant, and red means non-compliant.

Allowlists and blocklists are enforced to control access to systems, networks, and applications, ensuring only approved resources can be accessed

Blocklisting involves identifying and restricting access to known malicious or unauthorized entities, such as specific IP addresses, domains, or URLs. Allowlisting, on the other hand, permits access only to pre-approved, trusted sources, such as verified applications or network endpoints. Together, these measures help prevent unauthorized access and reduce exposure to security threats.

Implementation Suggestions:

Implement blocklists to deny access to known malicious websites, IP addresses, or domains using network firewalls and endpoint protection tools.
Use allowlists to restrict access to only approved applications and network services, particularly on critical systems.
Regularly review and update allowlists and blocklists to adapt to new threats and organizational needs.
Automate the management of allowlists and blocklists with security tools that leverage threat intelligence feeds.
Educate employees on the importance of using approved resources and the risks associated with unauthorized applications and websites.

Baseline configuration management is used to establish a secure, stable, and standardized configuration for IT systems, applications, and network components

This process includes identifying and documenting configuration settings essential for secure and efficient operations, creating a baseline that serves as a reference point. The baseline is used for managing system changes, updates, and configurations and acts as a benchmark to assess security posture and compliance. Regular reviews and updates of the baseline ensure it remains aligned with evolving security standards and organizational requirements.

Implementation Suggestions:

Document all initial hardware, software, and network configurations upon system setup.
Store baseline configurations in a centralized, access-controlled repository.
Regularly review and update the baseline to reflect changes in the environment, new security patches, or updates.
Monitor deviations from the baseline and investigate unauthorized changes.
Implement automated tools to help enforce and audit compliance with the baseline configuration.

Configuration change control processes are implemented to manage and track changes to the configuration of information systems and software applications

This process involves monitoring, evaluating, approving, implementing, and documenting modifications, such as changes to hardware, software, network settings, or system parameters. By ensuring that changes are properly authorized, tested, and recorded, Configuration Change Control reduces the risk of introducing errors, vulnerabilities, or disruptions to systems and operations.

Implementation Suggestions:

Establish a formal process for requesting, reviewing, and approving configuration changes.
Document all configuration changes, including the rationale, testing results, and approval details.
Conduct testing in a controlled environment before applying changes to production systems.
Use automated tools to monitor systems for unauthorized configuration changes.
Periodically audit change control records to verify compliance and identify potential process improvements.

Malware protection measures, including regular signature updates, are implemented to prevent, detect, and remove malicious software such as viruses, spyware, and ransomware

These measures safeguard computer systems, networks, and data from compromise while reducing the risk of business disruption caused by malware attacks.

Key components include deploying anti-malware tools, configuring firewalls and intrusion detection/prevention systems (IDS/IPS), and maintaining up-to-date malware signatures to counter emerging threats. User education plays a vital role in strengthening defenses against phishing and other malware delivery methods.

Implementation Suggestions:

Deploy and regularly update anti-malware software on all endpoint devices and servers.
Enable real-time scanning and automated updates for malware detection signatures.
Configure firewalls and IDS/IPS solutions to block known malicious traffic.
Conduct periodic user training to raise awareness of phishing, suspicious downloads, and other common malware tactics.
Establish and verify automated processes for downloading and applying malware signature updates across all systems.
Enable alerts to identify outdated or failed updates promptly.
Periodically review and test anti-malware solutions to ensure effectiveness against evolving threats.
Regularly update malware protection policies to address new vulnerabilities and threats.

Mobile Device Management (MDM) is used to secure and manage mobile devices, such as smartphones, tablets, and laptops, that are used within the organization

MDM enforces security policies, monitors device configurations, and protects sensitive information by implementing controls like device encryption, remote wipe capabilities, password policies, application management, and device tracking. These measures help safeguard organizational data, reduce the risk of unauthorized access, and mitigate potential data loss or breaches through mobile devices.

Implementation Suggestions:

Enforce device encryption and strong password policies on all managed mobile devices.
Enable remote wipe functionality to protect data if a device is lost or stolen.
Restrict the installation of unauthorized applications and enforce application whitelisting where possible.
Use device tracking features to monitor asset inventory and identify suspicious device activity.
Regularly update MDM software to address vulnerabilities and support new security features.