Guidelines for system hardening
161 controls in 4 sections in this part of the Australian Government Information Security Manual. Each control links to plain-English guidance, audit tips and cross-framework mappings.
161 controls
No controls on this page match.
Operating system hardening
55 controls- ISM-0341Disable automatic execution for removable mediaTurn off every feature that automatically runs or opens content when removable media such as a USB drive is connected, on workstations and servers alike.NCOSPSTS
- ISM-0343Disable writing to removable media and devices with no business requirementWith no business requirement to write to removable media and devices, turn writing off, using a device access control application or by disabling external communication interfaces.NCOSPSTS
- ISM-0345Disable external interfaces for direct memory accessDisable every external communication interface that allows direct memory access (DMA), such as FireWire, ExpressCard or Thunderbolt, whether or not anyone has a business use for it.NCOSPSTS
- ISM-0380Disable unneeded OS accounts and servicesOn each workstation and server, disable or remove whatever the operating system includes but the machine does not need, across user accounts, components, services and functionality.NCOSPSTS
- ISM-0382Prevent unprivileged human users uninstalling or disabling approved applicationsUnprivileged human users must be unable to uninstall or disable approved applications, including through self-service portals or per-user installs.NCOSPSTS
- ISM-0383Change default OS user accounts during setupDeal with every default account or credential in an operating system before initial setup ends, by changing, disabling or removing it, and that includes pre-configured accounts.NCOSPSTS
- ISM-0582Central logging of Windows security eventsSend security-relevant events from every Microsoft Windows workstation and server to a central logging facility, so they do not stay only in each machine's local event logs.NCOSPSTS
- ISM-0843Ensure workstation security with application controlRun application control on every workstation, so only explicitly approved software can execute and everything else is blocked.NCOSPSTS
- ISM-0846Users cannot disable, bypass or be exempted from application controlNo user can switch off, get around or be excused from application control; the only exception is while using a local administrator or break glass account.NCOSPSTS
- ISM-0955Implementing application control measuresApplication control must approve files by cryptographic hash, publisher certificate or path, in any combination; an allow rule based on anything else, such as a file name alone, does not count.NCOSPSTS
- ISM-1034Deploy HIPS or EDR on critical and high-value serversRun a HIPS or EDR solution on every critical server, such as domain controllers, and every high-value server, such as DNS, database, email, file and web servers.NCOSPSTS
- ISM-1341Implement HIPS or EDR on workstationsRun a host-based intrusion prevention system (HIPS) or an endpoint detection and response (EDR) solution on every workstation; signature-based antivirus alone does not meet this.NCOSPSTS
- ISM-1392Restrict changes to files approved by path rulesWhere application control uses path rules, only approved users may change the files those rules approve or write to the folders they approve.NCOSPSTS
- ISM-1406Use SOEs for workstations and serversBuild workstations and servers from standard operating environments (SOEs), which are standard builds of an operating system and its applications, not one-off manual setups.NCOSPSTS
- ISM-1407Ensure use of current OS versionsRun only the vendor's latest or previous release of each operating system on workstations and servers; anything older fails, even if patched and still supported.NCOSPSTS
- ISM-1408Use 64-bit operating systemsEvery operating system on a workstation or server must be a 64-bit version, so a 32-bit installation fails even on 64-bit hardware.NCOSPSTS
- ISM-1409Harden operating systems with ASD and vendor guidanceHarden operating systems using both ASD's and the vendor's hardening guidance, and where the two conflict, apply whichever setting is more restrictive.NCOSPSTS
- ISM-1416Implement software firewalls on workstations and servers to restrict connectionsEach workstation and server needs its own software firewall that blocks connections in both directions unless they belong to an application or service in the organisation's approved set.NCOSPSTS
- ISM-1417Ensure antivirus protection on workstations and serversWorkstation and server antivirus needs high signature and heuristic detection, reputation and ransomware functions, at least daily signature updates and regular fixed disk and removable media scans.NCOSPSTS
- ISM-1418Disable reading from removable media and devices with no business requirementWith no business requirement to read from removable media and devices, turn reading off, using a device access control application or by disabling external communication interfaces.NCOSPSTS
- ISM-1471Utilise publisher and product names in app controlAny publisher certificate rule in application control must name both the publisher and the product, never the publisher alone.NCOSPSTS
- ISM-1490Implement application control on internet-facing serversRun application control on every internet-facing server, meaning any server directly reachable from the internet, so only explicitly approved software can execute on it.NCOSPSTS
- ISM-1491Block unprivileged human users from running script execution enginesUnprivileged human users must be blocked from running script engines, including Windows Script Host, PowerShell, Command Prompt, wmic.exe and mshta.exe, and any others on the host.NCOSPSTS
- ISM-1492Enable exploit protection in operating systemsExploit protection built into each workstation and server operating system, such as data execution prevention and memory layout randomisation, must be on.NCOSPSTS
- ISM-1544Implement Microsoft's application blocklistImplement Microsoft's recommended application blocklist, so the applications it names, which can be used to get around application control, are actually blocked.NCOSPSTS
- ISM-1582Annual validation of application control rulesetsValidate each application control ruleset at least annually, no more than 12 months apart, confirming it still meets what the organisation requires of it.NCOSPSTS
- ISM-1584Prevent unprivileged users bypassing, disabling or modifying OS securityUnprivileged users must be unable to bypass, disable or change the security functions of workstation and server operating systems, such as the firewall and event logging.NCOSPSTS
- ISM-1588Annual review of standard operating environmentsAt least annually, review each standard operating environment (SOE) and produce an updated version, because a review that leaves the build unchanged does not meet this.NCOSPSTS
- ISM-1592Prevent unprivileged human users from installing unapproved applicationsUnprivileged human users must be unable to install applications that have not been approved, by any route, including per-user installers and marketplaces.NCOSPSTS
- ISM-1601Implement Microsoft Attack Surface Reduction rulesImplement all of Microsoft's attack surface reduction rules on Microsoft Windows workstations and servers in block mode, so they block the risky behaviours they target and do not merely report them.NCOSPSTS
- ISM-1608Scan third-party SOEs for malicious codeScan every standard operating environment (SOE) a third party supplies, checking it for both malicious code and malicious configurations.NCOSPSTS
- ISM-1621Disable or remove Windows PowerShell 2.0Windows PowerShell 2.0 must be disabled or removed on Windows workstations and servers, even where newer PowerShell versions are also installed.NCOSPSTS
- ISM-1622Ensure PowerShell uses Constrained Language ModeConfigure PowerShell on workstations and servers to use Constrained Language Mode, which keeps cmdlets working but limits scripts' access to .NET, COM and Windows APIs.NCOSPSTS
- ISM-1623Centralised logging of PowerShell activitiesSend all three PowerShell event types (module logging, script block logging and transcription) to the centralised event logging facility, not only to logs on each device.NCOSPSTS
- ISM-1624Protect PowerShell script block logsEncrypt PowerShell script block logs with Protected Event Logging, so their contents, which can include credentials, can be read only with the private key.NCOSPSTS
- ISM-1654Disable or remove Internet Explorer 11Make sure Internet Explorer 11 cannot run on any workstation or server by disabling or removing it, with no exception for older applications that depend on it.NCOSPSTS
- ISM-1655Ensure .NET Framework 3.5 is disabled or removedDisable or remove .NET Framework 3.5, with the .NET 2.0 and 3.0 it includes, on workstations and servers, even where an application still relies on it.NCOSPSTS
- ISM-1656Implement application control on non-internet-facing serversRun application control on every non-internet-facing server, such as internal file and database servers, so only explicitly approved software can execute on it.NCOSPSTS
- ISM-1657Restrict application execution to approved setOnly executables, libraries, scripts, installers, compiled HTML, HTML applications and control panel applets the organisation has approved may run; application control blocks the rest.NCOSPSTS
- ISM-1658Restrict execution of drivers via application controlApplication control must block any driver outside the organisation's approved set, even one with a valid signature.NCOSPSTS
- ISM-1659Implement Microsoft's vulnerable driver blocklistImplement Microsoft's vulnerable driver blocklist, so drivers it lists for known flaws or malicious behaviour are blocked from loading, even when validly signed.NCOSPSTS
- ISM-1660Central logging of application control eventsSend both allowed and blocked application control events to central logging, so the record shows what ran as well as what was stopped.NCOSPSTS
- ISM-1743Choose secure operating system vendorsUse operating systems only from vendors that have shown commitment to Secure by Design, Secure by Default, secure programming, and memory-safe languages or, less preferably, memory-safe practices.NCOSPSTS
- ISM-1745Enable security features for system protectionAll four boot protections must be on for workstations and servers, not just some of them: Early Launch Antimalware, Secure Boot, Trusted Boot and Measured Boot.NCOSPSTS
- ISM-1746Restrict file system permission changesWhere application control relies on path rules, only approved users can change file system permissions on the files and folders those rules approve.NCOSPSTS
- ISM-1870Implement application control for user profiles and temporary foldersApplication control must also cover user profiles and the temporary folders used by operating systems, web browsers and email clients, so unapproved files cannot run from them.NCOSPSTS
- ISM-1871Apply application control to all other locationsApply application control everywhere else on a system: all locations other than user profiles and the temporary folders of operating systems, web browsers and email clients.NCOSPSTS
- ISM-1889Central logging of command line eventsCentrally log the events recorded when a process starts, including the command line that launched it, on operating systems used on workstations and servers.NCOSPSTS
- ISM-1896Enable memory integrity in operating systemsMemory integrity, which runs the checks on kernel-mode code in an isolated virtual environment, must be enabled on workstations and servers.NCOSPSTS
- ISM-1914Ensure operating systems have approved configurationsDevelop an approved configuration for each operating system in use, apply it to the machines running that system and keep it current; a signed-off document alone does not meet this.NCOSPSTS
- ISM-1976Central logging of security events on macOSSend security-relevant events from Apple macOS workstations and servers to a central logging facility, so they do not stay only on each Mac.NCOSPSTS
- ISM-1977Central logging of security-relevant events on LinuxSend security-relevant events from every Linux workstation and server to a central logging facility, so they do not stay only on the host that produced them.NCOSPSTS
- ISM-2127Enforce driver digital signature verification before loadingCheck each driver's digital signature before it loads and enforce the result, so a driver that fails the check does not load, rather than only raising a warning.NCOSPSTS
- ISM-2128Limit kernel-mode code installation to privileged users who need itInstalling, loading or changing kernel-mode code, such as drivers, must be possible only for privileged users whose duties or functions need it, not all administrators.NCOSPSTS
- ISM-2129Centrally log WMI activity and event subscriptionsSend WMI activity to the centralised event logging facility, and make sure it includes every creation of a permanent event subscription.NCOSPSTS
Server application hardening
62 controls- ISM-1245Remove temporary installation files after installing server applicationsAfter a server application is installed, remove every temporary file its installation created, such as unpacked setup packages and staging folders.NCOSPSTS
- ISM-1246Harden server applications with ASD and vendor guidanceHarden each server application using both ASD's and the vendor's hardening guidance, and where the two conflict, apply whichever is most restrictive.NCOSPSTS
- ISM-1247Disable or remove unneeded accounts and features in server applicationsDisable or remove any user account, component, service or feature inside a server application that the application's role does not need.NCOSPSTS
- ISM-1249Run server applications under separate accounts with minimum privilegesGive each server application its own user account to run under, and grant that account only the privileges the application's functions need.NCOSPSTS
- ISM-1250Limit the file system access of accounts that run server applicationsLimit the file system access of the account each server application runs under, based on what that application needs on its server.NCOSPSTS
- ISM-1260Secure server applications by changing default credentialsBefore a server application's initial setup is finished, change, disable or remove each default account and credential, including any accounts set up in advance.NCOSPSTS
- ISM-1483Use latest release of internet-facing server applicationsRun the vendor's latest release of every internet-facing server application, not the previous release or an older supported version, even when that version is fully patched.NCOSPSTS
- ISM-1620Ensure privileged accounts are secured in ADMake every privileged user account a member of the built-in Protected Users security group, so its credential protections apply to that account automatically.NCOSPSTS
- ISM-1826Use Secure by Design and Secure by Default vendors for server applicationsServer applications must come from vendors that have shown a commitment to Secure by Design and Secure by Default, secure programming, and memory-safe languages (or, less preferably, practices).NCOSPSTS
- ISM-1827Use dedicated admin accounts for domain controllersUse separate domain administrator accounts kept only for managing AD DS domain controllers, and never use them to manage servers, workstations or any other system.NCOSPSTS
- ISM-1828Disable print spooler on AD DS domain controllersDisable the Print Spooler service on every AD DS domain controller, setting it so it cannot start rather than just stopping it.NCOSPSTS
- ISM-1829Ensure no passwords remain stored in Group Policy PreferencesFind and remove every password stored in Group Policy Preferences, so none remains in the policy files that every domain user can read.NCOSPSTS
- ISM-1830Central logging of security events for Microsoft AD infrastructure serversSend security-relevant events from AD DS domain controllers and AD CS, AD FS and Entra Connect servers to the central logging facility, not only to local logs.NCOSPSTS
- ISM-1832SPN configuration for Active Directory accountsSet Service Principal Names (SPNs) only on service accounts and computer accounts, so no account a person uses holds one.NCOSPSTS
- ISM-1833Limit privileges for user accounts in Active DirectoryProvision every user account, for a person or a service, with only the privileges its duties or function require, and nothing more.NCOSPSTS
- ISM-1834Ensure no duplicate SPNs in Active DirectoryRegister each Service Principal Name (SPN) on only one account in the domain, leaving no duplicates.NCOSPSTS
- ISM-1835Block delegation of privileged user accounts by marking them sensitiveSet 'Account is sensitive and cannot be delegated' on every privileged user account, so no service can use Kerberos delegation to act as that account on other services.NCOSPSTS
- ISM-1836Require Kerberos pre-authentication for user accountsRequire Kerberos pre-authentication on every user account, so none has the 'Do not require Kerberos preauthentication' option set.NCOSPSTS
- ISM-1838Do not use the UserPassword attribute on user accountsLeave the UserPassword attribute empty on every user account in Microsoft AD DS, including service accounts, and stop any tool or script writing to it.NCOSPSTS
- ISM-1839Secure account properties in Active DirectoryNever store a password in any account property that unprivileged users can access, such as the description or notes field of a user, service or computer account.NCOSPSTS
- ISM-1840Prevent reversible encryption of user passwordsKeep reversible encryption off for every user account password, in each AD DS domain password policy, every fine-grained password policy and each account's own options.NCOSPSTS
- ISM-1841Block unprivileged user accounts from adding machines to the domainUnprivileged user accounts must be unable to add computers to the AD DS domain, which by default any user can do for up to 10 computers.NCOSPSTS
- ISM-1842Use dedicated privileged service accounts to add machines to the domainAdd machines to the AD DS domain only with privileged service accounts kept for that one job, never with administrators' own accounts or other service accounts.NCOSPSTS
- ISM-1843Annual review of user accounts with unconstrained delegationReview every user account trusted for unconstrained delegation at least annually; keep only those with both an SPN and a demonstrated business need, and remove the rest.NCOSPSTS
- ISM-1844Do not trust computer accounts other than domain controllers for delegationSet every computer account except domain controllers to 'Do not trust this computer for delegation', allowing neither unconstrained nor constrained delegation.NCOSPSTS
- ISM-1845Remove disabled user accounts from all security groupsRemove a user account from every security group as part of disabling it, because disabling alone leaves all of its group memberships in place.NCOSPSTS
- ISM-1846Restrict Pre-Windows 2000 access group membershipKeep user accounts, including service accounts, out of the Pre-Windows 2000 Compatible Access group, whether added directly or through a nested group.NCOSPSTS
- ISM-1916Ensure server application configurations are approvedDevelop an approved configuration for each server application, apply it to every installation, and keep the configuration current and every installation matching it.NCOSPSTS
- ISM-1926Restrict identity servers to their designed role onlyKeep AD DS domain controllers and AD CS, AD FS and Entra Connect servers to their designed role, with nothing else installed unless it is security related.NCOSPSTS
- ISM-1927Limit identity server access to privileged users requiring itAllow only privileged users whose duties require it to log on to or manage AD DS domain controllers and AD CS, AD FS and Entra Connect servers.NCOSPSTS
- ISM-1928Encrypt and restrict access to Microsoft AD and Entra Connect server backupsEncrypt backups of AD DS domain controllers and AD CS, AD FS and Entra Connect servers with ASD-approved cryptography, store them securely and restrict them to backup administrators.NCOSPSTS
- ISM-1929Ensure LDAP signing on AD DS domain controllersTurn on LDAP signing on every AD DS domain controller by requiring it, so the domain controller refuses unsigned LDAP binds.NCOSPSTS
- ISM-1930Prevent storing passwords in Group Policy PreferencesMake sure no Group Policy editing tool on any computer can save a password in Group Policy Preferences, rather than relying on administrators to leave the password field blank.NCOSPSTS
- ISM-1931Ensure SID filtering for domain and forest trustsKeep SID filtering enabled on every external domain trust and forest trust, so sign-ins arriving over the trust cannot carry SIDs from outside the trusted domain or forest.NCOSPSTS
- ISM-1932Limit service accounts with SPNs in Active DirectoryKeep the number of service accounts with a Service Principal Name (SPN) to the minimum, removing every SPN that no current service needs.NCOSPSTS
- ISM-1933No DCSync permissions for service accounts with an SPNService accounts that have a Service Principal Name (SPN) must hold no DCSync permissions, the replication rights that let an account pull password hashes from a domain controller.NCOSPSTS
- ISM-1934Six-monthly review and removal of DCSync user permissionsReview user accounts holding DCSync permissions no more than six months apart, and remove the permissions from any account with no ongoing need for them.NCOSPSTS
- ISM-1935Prevent unconstrained delegation on computer accountsDo not configure any computer account for unconstrained delegation, which lets a computer act as connecting users on any service.NCOSPSTS
- ISM-1936Prevent usage of sIDHistory in user accountsKeep the sIDHistory attribute empty on every user account in Microsoft AD DS, and do not rely on it to carry access through a domain migration.NCOSPSTS
- ISM-1937Weekly audit of sIDHistory in user accountsAt least weekly, check every user account in each AD DS domain for a value in sIDHistory, the attribute that ISM-1936 says must not be used.NCOSPSTS
- ISM-1938No write or modify permissions on AD objects for the Domain Computers groupRemove every permission that lets Domain Computers change a directory object, such as Full control, Write or Modify permissions, anywhere in Microsoft Active Directory.NCOSPSTS
- ISM-1939Minimise user accounts in Domain Admins and other highly privileged groupsCut the number of user accounts in Domain Admins, Enterprise Admins and other highly privileged groups to the fewest the work truly needs.NCOSPSTS
- ISM-1940Keep service accounts out of Domain Admins and other highly privileged groupsKeep every service account out of Domain Admins, Enterprise Admins and any other highly privileged group, whether added directly or through a nested group.NCOSPSTS
- ISM-1941Keep computer accounts out of Domain Admins and other highly privileged groupsKeep every computer account out of Domain Admins, Enterprise Admins and any other highly privileged group, whether added directly or through a nested group.NCOSPSTS
- ISM-1942Keep the Domain Computers group out of privileged and highly privileged groupsThe built-in Domain Computers group, which holds every domain-joined computer except domain controllers, must not be a member of any privileged or highly privileged group.NCOSPSTS
- ISM-1943Enforce certificate and user mapping in AD servicesEnforce strong certificate mapping, so a certificate signs a user in only when tied to that account by something unique, such as the account's SID, never by name or email alone.NCOSPSTS
- ISM-1944Remove EDITF_ATTRIBUTESUBJECTALTNAME2 flag from AD CS certification authoritiesRemove the EDITF_ATTRIBUTESUBJECTALTNAME2 flag from every AD CS certification authority, so no requester can add extra names to a certificate through request attributes.NCOSPSTS
- ISM-1945Remove enrollee supplies subject flag from templatesRemove the CT_FLAG_ENROLLEE_SUPPLIES_SUBJECT flag ('Supply in the request') from every certificate template, so the subject comes from Active Directory, not from the requester.NCOSPSTS
- ISM-1946Restrict write access to certificate templatesUnprivileged user accounts must have no way to change any certificate template, whether through a direct permission, a group, inheritance or ownership.NCOSPSTS
- ISM-1947Remove user authentication from extended key usagesRemove Extended Key Usages (EKUs) that enable user authentication; the risk is greatest where the requester supplies the names, as one user could then sign in as another.NCOSPSTS
- ISM-1948Certificate manager approval for templates allowing supplied SANsRequire CA certificate manager approval on every certificate template that lets the requester supply a Subject Alternative Name, so each such request waits for review.NCOSPSTS
- ISM-1949Use a dedicated service account for AD FS administrationGive AD FS servers a service account of their own for administration, and never use that account to administer any other server or system.NCOSPSTS
- ISM-1950Disable soft matching after synchronisationOnce initial synchronisation activities are finished, disable soft matching between Microsoft AD DS and Entra ID, so accounts no longer link because their sign-in names or email addresses match.NCOSPSTS
- ISM-1951Disable hard match takeover in Microsoft Entra ConnectKeep hard match takeover disabled for Microsoft Entra Connect servers, so synchronisation cannot use a matching immutable ID to take control of an account managed in Entra ID.NCOSPSTS
- ISM-1952Prevent synchronisation of privileged accountsKeep privileged user accounts out of synchronisation between Microsoft AD DS and Entra ID in both directions, so each directory's privileged accounts exist only in that directory.NCOSPSTS
- ISM-1978Centrally log server application security events on internet-facing serversSend security-relevant events from server applications on internet-facing servers, such as web or email server software, to the central event logging facility, not just operating system logs.NCOSPSTS
- ISM-1979Centrally log server application security events on non-internet-facing serversSend security-relevant events from server applications on non-internet-facing servers, such as database or directory software, to the central event logging facility, not just operating system logs.NCOSPSTS
- ISM-2010Ensure SPNs use strong encryption in AD servicesService accounts that have a Service Principal Name (SPN) must use AES for encryption, so tickets for their services are encrypted with AES rather than RC4 or DES.NCOSPSTS
- ISM-2115Restrict server application extensions to an approved setAllow only extensions the organisation has approved, such as plugins and modules, to run in each server application.NCOSPSTS
- ISM-2130Disabling or hardening AD CS web enrolment interfacesTurn off AD CS web enrolment unless something needs it, and make any that stays accept only HTTPS, with Extended Protection for Authentication set to Required.NCOSPSTS
- ISM-2131Quarterly certificate template reviews to remediate misconfigurationsReview every certificate template at least every three months, and fix any misconfiguration that could allow privilege escalation or certificates issued to the wrong people.NCOSPSTS
- ISM-2132Central logging of certificate enrolment requests, template and AD CS configuration changesSend AD CS enrolment events to central logging, covering successful and failed certificate requests and every change to certificate templates or AD CS configuration.NCOSPSTS
User application hardening
37 controls- ISM-0938Use Secure by Design and Secure by Default vendors for user applicationsUse vendors that have shown commitment to Secure by Design and Secure by Default for user applications, including secure programming and memory-safe languages or, less preferably, practices.NCOSPSTS
- ISM-1235Restrict user application extensionsUser applications must only accept extensions from a set the organisation has approved, with everything else blocked rather than just discouraged.NCOSPSTS
- ISM-1412Harden web browsers with ASD and vendor guidanceHarden every web browser using both ASD's and the vendor's hardening guidance, and where they disagree on a setting, apply the most restrictive one.NCOSPSTS
- ISM-1467Use latest releases of browsers, email, office, PDF and security applicationsKeep every email client, office productivity suite, PDF application, security product and web browser, plus their extensions, on the vendor's latest release, not merely a supported one.NCOSPSTS
- ISM-1470Disable unneeded accounts, components, services and application functionalityAnything a user application includes but does not need, whether a user account, component, service or function, must be disabled or removed.NCOSPSTS
- ISM-1485Prevent web browsers from processing adsStop web browsers loading or running advertisements served from the internet, on every site and whether the device is on the corporate network or elsewhere.NCOSPSTS
- ISM-1486Restrict Java processing in web browsersWeb browsers must not load or run Java content, such as applets, from any internet site, even if a person would accept a prompt; JavaScript is a different language and is not covered.NCOSPSTS
- ISM-1487Restrict write access to trusted locations to macro vetting usersLimit write and modify access to Trusted Locations to the privileged human users whose job is checking Microsoft Office macros for malicious code.NCOSPSTS
- ISM-1488Blocking internet-originating macros in Office filesBlock macros in Microsoft Office files that come from the internet, such as downloads and outside email attachments, so nobody can choose to run them.NCOSPSTS
- ISM-1489Lock Microsoft Office macro security settings against user changesLock Microsoft Office's macro security settings so that human users cannot change them, whether through the Trust Centre, the registry or a trust prompt.NCOSPSTS
- ISM-1542Prevent Microsoft Office from activating OLE packagesSet Microsoft Office so that Object Linking and Embedding (OLE) packages inside documents cannot be activated, even when a reader tries to open one.NCOSPSTS
- ISM-1585Lock web browser security settings against human user changesLock web browser security settings through central policy so that no person using the system, standard user or not, can change them.NCOSPSTS
- ISM-1667Prevent child processes in Microsoft OfficeBlock Microsoft Office from starting other programs as child processes, with no exception for particular applications, users or business tools.NCOSPSTS
- ISM-1668Prevent Microsoft Office from creating executable filesBlock Microsoft Office from creating executable content, meaning files that can run as code, whatever prompts Office to write them.NCOSPSTS
- ISM-1669Prevent Microsoft Office from injecting codeBlock Microsoft Office from injecting code into other processes, meaning it cannot place code inside another running program to run there.NCOSPSTS
- ISM-1670Prevent PDF applications from creating child processesBlock every PDF application from creating child processes, so it cannot start other programs such as a command shell or script host.NCOSPSTS
- ISM-1671Disable Office macros for users lacking a demonstrated business requirementDisable Microsoft Office macros for every human user except those with a demonstrated business requirement, so macro use is an exception that has to be shown.NCOSPSTS
- ISM-1672Enable antivirus scanning for Office macrosTurn on Microsoft Office's antivirus scanning of macros, so the antivirus product checks macros, including what they do as they run.NCOSPSTS
- ISM-1673Prevent Win32 API calls by Office macrosBlock Microsoft Office macros from making Win32 API calls, the Windows functions a macro could otherwise use to act beyond Office.NCOSPSTS
- ISM-1674Ensuring secure execution of Microsoft Office macrosBlock every Microsoft Office macro except those running in a sandboxed environment or a Trusted Location, or digitally signed by a trusted publisher.NCOSPSTS
- ISM-1675Prevent enabling untrusted Microsoft Office macrosGive users no way to enable a Microsoft Office macro signed by an untrusted publisher from the Message Bar or the Backstage View.NCOSPSTS
- ISM-1676Validate Microsoft Office trusted publishers list at least annuallyAt least annually, validate Microsoft Office's list of trusted publishers, confirming each publisher should still be trusted and nothing unapproved was added.NCOSPSTS
- ISM-1748Lock email client security settings against user changesHuman users must have no way to change an email client's security settings: a setting a person can alter is not locked.NCOSPSTS
- ISM-1806Change, disable or remove default user application credentials during setupUser applications must not go into use with default accounts or credentials still working: change, disable or remove them during initial setup, pre-configured accounts included.NCOSPSTS
- ISM-1823Lock Office productivity suite security settings against user changesHuman users must not be able to change any office productivity suite security setting, whether in the application or wherever those settings are stored.NCOSPSTS
- ISM-1824Lock PDF application security settings against user changesLock every PDF application's security settings so that human users cannot change them, whether in the application's preferences, the registry or a trust prompt.NCOSPSTS
- ISM-1825Lock security product settings against changes by human usersLock the security settings of security products, such as antivirus, HIPS, software firewalls and device access control applications, so that no person using the system can change them.NCOSPSTS
- ISM-1859Hardening Office productivity suitesHarden office productivity suites using both ASD's and the vendor's guidance, and apply whichever is more restrictive wherever the two conflict.NCOSPSTS
- ISM-1860Harden PDF applications with ASD and vendor guidanceHarden every PDF application using both ASD's and the vendor's hardening guidance, and where the two disagree on a setting, apply the more restrictive one.NCOSPSTS
- ISM-1890Ensure macros are free of malicious codeBefore any Microsoft Office macro is digitally signed or placed in a Trusted Location, check it for malicious code, including each new version.NCOSPSTS
- ISM-1891Restrict non-V3 signed macros in Microsoft OfficeGive users no way to enable a Microsoft Office macro whose signature is not a V3 signature, from either the Message Bar or the Backstage View.NCOSPSTS
- ISM-1915Ensure user application configurations are approvedUser applications must run on approved configurations that are developed, put in place and kept current, rather than on whatever settings the installer left.NCOSPSTS
- ISM-2110Hardening user applications with ASD and vendor guidanceHarden user applications using both ASD's and the vendor's hardening guidance, and where they conflict, apply whichever is most restrictive, whoever wrote it.NCOSPSTS
- ISM-2111Remove temporary installation files post-installationOnce a user application is installed, every temporary file its installation process created must be removed, leaving none behind.NCOSPSTS
- ISM-2112AI applications processing classified data cannot directly access public dataAI applications that process classified data, including OFFICIAL: Sensitive, must not be able to reach external public data sources directly, such as through web search.OSPSTS
- ISM-2113Configuring AI applications to require human approval before high-impact actionsAI applications must be configured so that a person approves any sensitive or high-impact action before the application carries it out.NCOSPSTS
- ISM-2114Monitor baselines for AI application performanceSet baselines for how each AI application is expected to behave and perform, then monitor it against them so unexpected deviations are noticed.NCOSPSTS
Virtualisation hardening
7 controls- ISM-1460Secure by design vendor isolation mechanismsHypervisors and other isolation software sharing physical hardware must come from a vendor with a demonstrated commitment to Secure by Design and Secure by Default, including secure, memory-safe code.NCOSPSTS
- ISM-1461Same classification and security domain for shared isolation hostsWhere SECRET or TOP SECRET environments share a physical server through a hypervisor or similar, the server and every environment on it must have one classification and security domain.STS
- ISM-1604Harden software isolation mechanisms sharing physical computing resourcesHarden the configuration of isolation software sharing physical hardware, such as a hypervisor: remove functionality it does not need and restrict access to its administrative interface.NCOSPSTS
- ISM-1605Harden the operating system beneath software isolation mechanismsHarden the operating system underneath any hypervisor, container engine or other isolation software that lets several environments share one physical computer.NCOSPSTS
- ISM-1606Patch isolation mechanisms and underlying operating systems promptlyPromptly apply patches, updates or vendor mitigations for vulnerabilities to isolation software sharing physical hardware, such as a hypervisor, and to the operating system under it.NCOSPSTS
- ISM-1607Integrity monitoring and logging for isolation mechanismRun integrity monitoring and centralised event logging for isolation software sharing physical resources, such as a hypervisor or container engine, and for the operating system under it.NCOSPSTS
- ISM-1848Replace unsupported software-based isolation mechanisms sharing physical resourcesReplace isolation software that shares physical hardware, such as a hypervisor, or the operating system under it, when its vendor stops supporting it.NCOSPSTS
Back to the full Information Security Manual (ISM) control list, or browse the complete control library.




