![]() ![]() Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1048: Application Isolation and Sandboxing) Restrict execution of code to a virtual environment on or in transit to an endpoint system. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account. Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Example implementations can include: disabling default accounts or making them unusable. Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. Safeguard 9.1: Ensure Use of Only Fully Supported Browsers and Email Clients: Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.Īpply the Principle of Least Privilege to all systems and services. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool. ![]() Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis. Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard. Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. We recommend the following actions be taken:Īpply appropriate updates provided by Mozilla to vulnerable systems immediately after appropriate testing. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights. Depending on the privileges associated with the user, an attacker could then install programs view, change, or delete data or create new accounts with full user rights. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. CVE-2022-42931: Username saved to a plaintext file on disk.CVE-2022-42930: Race condition in DOM Workers.CVE-2022-42929: Denial of Service via window.print. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |