Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Google Chrome 156.0.8078.48

3 new settings, 5 changed since 155.0.8059.85.

Wording or translations only

7 settings · compared with 155.0.8059.85
  • Computer and user · Google\Google Chrome
    Registry key: Software\Policies\Google\Chrome · Value name: EditBookmarksEnabled
    • Description Setting the policy to [removed: True][added: Enabled] or leaving it unset lets users add, remove, modify, or upload bookmarks. Setting the policy to [removed: False][added: Disabled] means users can't add, remove, modify or upload bookmarks. They can still …
      Whole description, marked

      Setting the policy to [removed: True][added: Enabled] or leaving it unset lets users add, remove, modify, or upload bookmarks. Setting the policy to [removed: False][added: Disabled] means users can't add, remove, modify or upload bookmarks. They can still use existing bookmarks.

  • Computer and user · Google\Google Chrome\Content settings
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … on valid site url patterns, please s…[removed: JavaScript JIT][added: Policy exceptions can be set for specifi…] policy [removed: exceptions will][added: set for] only [added: subdomain.site.com applies to subdomain.site.com withou…]be [removed: enforced at a site granularity (eTLD+1). A][added: isolated from its parent site, it may inherit the] policy set [added: on site.com. Exceptions may also not take effect ]for [removed: only subdomain.site.com][added: frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites]…
      Whole description, marked

      Allows you to set a list of site url patterns that specify sites which are allowed to run JavaScript with JIT (Just In Time) compiler enabled. For detailed information on valid site url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed. [removed: JavaScript JIT][added: Policy exceptions can be set for specific subdomains as well as entire sites. For example, a] policy [removed: exceptions will][added: set for] only [added: subdomain.site.com applies to subdomain.site.com without affecting site.com. In some cases where a subdomain cannot ]be [removed: enforced at a site granularity (eTLD+1). A][added: isolated from its parent site, it may inherit the] policy set [added: on site.com. Exceptions may also not take effect ]for [removed: only subdomain.site.com][added: frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites] will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptJitSetting, if set, or default] to [removed: site.com][added: the profile's JavaScript JIT setting. To enforce exceptions, Google Chrome may place sites or subdomains whose setting differs from the default into dedicated processes. This can increase memory usage, especially on Android] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since [removed: they both resolve][added: each matching origin may be isolated separately. Isolated subdomains also cannot use document.domain] to [removed: the same eTLD+1 (site.com)][added: access their parent site. Note: In versions 155 and earlier, policy exceptions were only enforced at a site granularity (eTLD+1). A policy set] for [removed: which there is no policy. In this case, policy must][added: only subdomain.site.com did not take effect, even for subdomain.site.com; it had to] be set on site.com to apply [removed: correctly for ][added: to ]both site.com and subdomain.site.com. This policy applies on a frame-by-frame basis and not based on top level origin url alone, so e.g. if site-one.com is listed in the JavaScriptJitAllowedForSites policy but site-one.com loads a frame containing site-two.com then site-one.com will have JavaScript JIT enabled, but site-two.com will use the policy from DefaultJavaScriptJitSetting, if set, or default to JavaScript JIT enabled.[added: Blocklist entries have higher priority than allowlist entries, which in turn have higher priority than the configured default value.] If this policy is not set for a site then the policy from DefaultJavaScriptJitSetting applies to the site, if set, otherwise Javascript JIT is enabled for the site. Example value: [*.]example.edu

  • Computer and user · Google\Google Chrome\Content settings
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … information on valid url patterns, p…[removed: JavaScript JIT][added: Policy exceptions can be set for specifi…] policy [removed: exceptions will][added: set for] only [added: subdomain.site.com applies to subdomain.site.com withou…]be [removed: enforced at a site granularity (eTLD+1). A][added: isolated from its parent site, it may inherit the] policy set [added: on site.com. Exceptions may also not take effect ]for [removed: only subdomain.site.com][added: frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites]…
      Whole description, marked

      Allows you to set a list of site url patterns that specify sites which are not allowed to run JavaScript JIT (Just In Time) compiler enabled. Disabling the JavaScript JIT will mean that Google Chrome may render web content more slowly, and may also disable parts of JavaScript including WebAssembly. Disabling the JavaScript JIT may allow Google Chrome to render web content in a more secure configuration. For detailed information on valid url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed. [removed: JavaScript JIT][added: Policy exceptions can be set for specific subdomains as well as entire sites. For example, a] policy [removed: exceptions will][added: set for] only [added: subdomain.site.com applies to subdomain.site.com without affecting site.com. In some cases where a subdomain cannot ]be [removed: enforced at a site granularity (eTLD+1). A][added: isolated from its parent site, it may inherit the] policy set [added: on site.com. Exceptions may also not take effect ]for [removed: only subdomain.site.com][added: frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites] will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptJitSetting, if set, or default] to [removed: site.com][added: the profile's JavaScript JIT setting. To enforce exceptions, Google Chrome may place sites or subdomains whose setting differs from the default into dedicated processes. This can increase memory usage, especially on Android] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since [removed: they both resolve][added: each matching origin may be isolated separately. Isolated subdomains also cannot use document.domain] to [removed: the same eTLD+1 (site.com)][added: access their parent site. Note: In versions 155 and earlier, policy exceptions were only enforced at a site granularity (eTLD+1). A policy set] for [removed: which there is no policy. In this case, policy must][added: only subdomain.site.com did not take effect, even for subdomain.site.com; it had to] be set on site.com to apply [removed: correctly for ][added: to ]both site.com and subdomain.site.com. This policy applies on a frame-by-frame basis and not based on top level origin url alone, so e.g. if site-one.com is listed in the JavaScriptJitBlockedForSites policy but site-one.com loads a frame containing site-two.com then site-one.com will have JavaScript JIT disabled, but site-two.com will use the policy from DefaultJavaScriptJitSetting, if set, or default to JavaScript JIT enabled.[added: Blocklist entries have higher priority than allowlist entries, which in turn have higher priority than the configured default value.] If this policy is not set for a site then the policy from DefaultJavaScriptJitSetting applies to the site, if set, otherwise JavaScript JIT is enabled for the site. Example value: [*.]example.edu

  • Computer and user · Google\Google Chrome\Content settings
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … on valid site url patterns, please see …[removed: JavaScript optimization policy exceptions…][added: Policy exceptions can be set for specific…] policy set for only subdomain.site.com [added: applies to subdomain.site.com without affe…]will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptOpti…] to [removed: site.com][added: the profile's JavaScript optimization setting. To enforce exceptio…] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since …
      Whole description, marked

      Allows you to set a list of site url patterns that specify sites for which advanced JavaScript optimizations are enabled. For detailed information on valid site url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed. [removed: JavaScript optimization policy exceptions will only be enforced at a site granularity (eTLD+1). A][added: Policy exceptions can be set for specific subdomains as well as entire sites. For example, a] policy set for only subdomain.site.com [added: applies to subdomain.site.com without affecting site.com. In some cases where a subdomain cannot be isolated from its parent site, it may inherit the policy set on site.com. Exceptions may also not take effect for frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites ]will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptOptimizerSetting, if set, or default] to [removed: site.com][added: the profile's JavaScript optimization setting. To enforce exceptions, Google Chrome may place sites or subdomains whose setting differs from the default into dedicated processes. This can increase memory usage, especially on Android] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since [removed: they both resolve to the same eTLD+1 (site.com) for which there is no policy.][added: each matching origin may be isolated separately. Isolated subdomains also cannot use document.domain to access their parent site. Note:] In [removed: this case,][added: versions 138 and earlier, policy exceptions were only enforced at a site granularity (eTLD+1). A] policy[removed: must][added: set for only subdomain.site.com did not take effect, even for subdomain.site.com; it had to] be set on site.com to[removed: ][added: ]apply [removed: correctly for ][added: to ]both site.com and[removed: ][added: ]subdomain.site.com. This policy applies on a frame-by-frame basis and not based on top level origin url alone, so e.g. if site-one.com is listed in the JavaScriptOptimizerAllowedForSites policy but site-one.com loads a frame containing site-two.com then site-one.com will have JavaScript optimizations enabled, but site-two.com will use the policy from DefaultJavaScriptOptimizerSetting, if set, or default to JavaScript optimizations enabled. Blocklist entries have higher priority than allowlist entries, which in turn have higher priority than the configured default value. If this policy is not set for a site then the policy from DefaultJavaScriptOptimizerSetting applies to the site, if set, otherwise Javascript optimization is enabled for the site. Example value: [*.]example.edu

  • Computer and user · Google\Google Chrome\Content settings
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … information on valid url patterns, plea…[removed: JavaScript optimization policy exceptions…][added: Policy exceptions can be set for specific…] policy set for only subdomain.site.com [added: applies to subdomain.site.com without affe…]will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptOpti…] to [removed: site.com][added: the profile's JavaScript optimization setting. To enforce exceptio…] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since …
      Whole description, marked

      Allows you to set a list of site url patterns that specify sites for which advanced JavaScript optimizations are disabled. Disabling JavaScript optimizations will mean that Google Chrome may render web content more slowly. For detailed information on valid url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed. [removed: JavaScript optimization policy exceptions will only be enforced at a site granularity (eTLD+1). A][added: Policy exceptions can be set for specific subdomains as well as entire sites. For example, a] policy set for only subdomain.site.com [added: applies to subdomain.site.com without affecting site.com. In some cases where a subdomain cannot be isolated from its parent site, it may inherit the policy set on site.com. Exceptions may also not take effect for frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites ]will [removed: not correctly apply][added: instead use the policy from DefaultJavaScriptOptimizerSetting, if set, or default] to [removed: site.com][added: the profile's JavaScript optimization setting. To enforce exceptions, Google Chrome may place sites or subdomains whose setting differs from the default into dedicated processes. This can increase memory usage, especially on Android] or [removed: subdomain.site.com][added: when a wildcard pattern matches many subdomains,] since [removed: they both resolve to the same eTLD+1 (site.com) for which there is no policy.][added: each matching origin may be isolated separately. Isolated subdomains also cannot use document.domain to access their parent site. Note:] In [removed: this case,][added: versions 138 and earlier, policy exceptions were only enforced at a site granularity (eTLD+1). A] policy[removed: must][added: set for only subdomain.site.com did not take effect, even for subdomain.site.com; it had to] be set on site.com to[removed: ][added: ]apply [removed: correctly for ][added: to ]both site.com and[removed: ][added: ]subdomain.site.com. This policy applies on a frame-by-frame basis and not based on top level origin url alone, so e.g. if site-one.com is listed in the JavaScriptOptimizerBlockedForSites policy but site-one.com loads a frame containing site-two.com then site-one.com will have JavaScript optimizations disabled, but site-two.com will use the policy from DefaultJavaScriptOptimizerSetting, if set, or default to JavaScript optimizations enabled. Blocklist entries have higher priority than allowlist entries, which in turn have higher priority than the configured default value. If this policy is not set for a site then the policy from DefaultJavaScriptOptimizerSetting applies to the site, if set, otherwise JavaScript optimization is enabled for the site. Example value: [*.]example.edu

  • Computer and user · Google\Google Chrome\Cryptography compliance policies
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … TLS 1.3 and QUIC; it does not affect earlier versions of TLS. [added: This policy can be set for the machine and for the user. If set for the user, this policy only affects network requests initiated by the user profile, and may not affect network requests made by Google Chrome to carry out browser-wide background tasks; those are controlled by the machi…]Example value: cnsa
      Whole description, marked

      This policy configures Google Chrome to order its preferred encryption ciphers in TLS 1.3 to reflect a preference for algorithms that have been approved by a specific compliance regime. Setting this policy does not guarantee that any specific algorithms will be negotiated. This policy exists to allow server operators who wish to support clients with and without compliance requirements to differentiate between those clients, and only use certain non-default algorithms with increased cryptographic strength for those explicitly configured to prefer them. Setting the policy to 'cnsa' configures Google Chrome to prefer ciphers required for compliance with the Commercial National Security Algorithm Suite versions 1.0 and 2.0 (CNSA 1.0 and 2.0). Not setting the policy, or setting it to 'default', configures Google Chrome to use its default ciphers. Setting this policy is not required for security. The default cryptography used by Google Chrome is strong enough to withstand a brute force attack using the entire power of the Sun. Setting this policy will cause Google Chrome to be slower when accessing websites. This policy only affects TLS 1.3 and QUIC; it does not affect earlier versions of TLS. [added: This policy can be set for the machine and for the user. If set for the user, this policy only affects network requests initiated by the user profile, and may not affect network requests made by Google Chrome to carry out browser-wide background tasks; those are controlled by the machine-level value. If this policy is set at both the machine level and the user level, the machine-level value applies, unless the policy precedence order has been changed by the CloudUserPolicyOverridesCloudMachinePolicy policy. For versions 155 and below, this policy is machine-wide only. ]Example value: cnsa

  • Computer and user · Google\Google Chrome\Cryptography compliance policies
    Registry key: Software\Policies\Google\Chrome · Value name: Not specified
    • Description … TLS 1.3 and QUIC; it does not affect earlier versions of TLS. [added: This policy can be set for the machine and for the user. If set for the user, this policy only affects network requests initiated by the user profile, and may not affect network requests made by Google Chrome to carry out browser-wide background tasks; those are controlled by the machi…]Example value: cnsa2
      Whole description, marked

      This policy configures Google Chrome to order its preferred key agreement algorithms (supported groups) in TLS 1.3 to reflect a preference for algorithms that have been approved by a specific compliance regime. Setting this policy does not guarantee that any specific algorithms will be negotiated. This policy exists to allow server operators who wish to support clients with and without compliance requirements to differentiate between those clients, and only use certain non-default algorithms with increased cryptographic strength for those explicitly configured to prefer them. Setting the policy to 'cnsa2' configures Google Chrome to prefer key exchange methods required for compliance with the Commercial National Security Algorithm Suite 2.0 (CNSA 2.0). Not setting the policy, or setting it to 'default', configures Google Chrome to use its default key exchange methods. Setting this policy is not required for security. The default cryptography used by Google Chrome is strong enough to withstand a brute force attack using the entire power of the Sun. Setting this policy will cause Google Chrome to be slower when accessing websites. This policy only affects TLS 1.3 and QUIC; it does not affect earlier versions of TLS. [added: This policy can be set for the machine and for the user. If set for the user, this policy only affects network requests initiated by the user profile, and may not affect network requests made by Google Chrome to carry out browser-wide background tasks; those are controlled by the machine-level value. If this policy is set at both the machine level and the user level, the machine-level value applies, unless the policy precedence order has been changed by the CloudUserPolicyOverridesCloudMachinePolicy policy. For versions 155 and below, this policy is machine-wide only. ]Example value: cnsa2

Cite this release

The exact files ChangeIntel read; they never change at this address
Release
Google Chrome 156.0.8078.48 (stable)
Published
26 Oct 2026
Collected
27 Oct 2026 08:13 UTC
Templates
2 ADMX files, 36 ADML files in 18 languages
Package
policy_templates.zip
File set SHA-256
1376a9ec58cd0f91a06c4362c359daf6819d325e1db649de11aa0d2702319b7c
Snapshot
e98d7c9f6c07fa16ad203f23fb10c1fabc5519f545263acacf616e846cef8a04

Changed template files

19
FileChangeSHA-256 beforeSHA-256 after
chrome.admxChanged22f8bde7d1d655fe53474132aac1f1d65c3cf37a94cac1ffd19c94aa306dd84f0a458fd11886b5edae8611e3ccd45d278d8473a777cff5ee05116399b17eb5f7
de-DE/chrome.admlChanged02621e4e8bedcc2a812c09e3bc794bfb3baf7daeee4dfdc23f34d48c733993680f346ef8e6787507ca6c63ae027d1d721d5846574694b32283b43b7b85c813d7
en-US/chrome.admlChangedb6a520a148cb3c93ed85a19d82931b51e52233bd5e355c3dc141840165e86393715da9d50f0185d7fc16b1ab6c967c12cf90c67f3d05f226f9c11a6ed0ce9544
es-419/chrome.admlChangede75c1399d1c11a299db187d3f779c20c6a369f7167d0a20a65f7ca5287a245cdeaf0703ba980ef803e79c93b28ebde342ebedd8555a90f4951443ea6c3a90440
es-ES/chrome.admlChanged9016c190072f437c80d25791796e6dd1500753c9b88ae2ea278ea94b249c555869aa13c4bd0a4e4fcb8fae58a87f863c30ed551c647079b528d14b612455658a
fr-FR/chrome.admlChanged87c313c115aebe442e88c2228589134877d67e69b4126b5d7c4c8c0d45a8199ffa929d72031c98a51b4bd265019f3c08d191be343a3c89e1991f5a726bc53985
id-ID/chrome.admlChanged4bfb79fd324aff5b3f990c337bb38d7a133c78b1c7276594201be6d9d138a5fe64a55203305f2847506c65a2fc9085564c9f967d4ad898226721794cc72cf63c
it-IT/chrome.admlChanged1a3b97b6ab8cbce5d0a4be2b384802266a827e716208c0ab354029e79022bf9ebbd7c4717b0cbcf5b5021dbe6323a860c9ee9f421cbf1097ddbc04136b17b215
ja-JP/chrome.admlChangede7d338040a9709e2b01a1c5fa9b181fb7b169150b9c40f453ffd7d6cc01dd45d89354644af37dc2fa170e356d965b36369f186b88209b76e7b3ed95640751e08
ko-KR/chrome.admlChanged3bb96f862d852a5d1810e72d95723c9d925039f82308abe219e9c21e60fb34b1444451e2335ff349e31fd5bcb9a52f3243a214c1c8c1eaa3e5505bbd76c74fbd
nl-NL/chrome.admlChanged97473f8c1da4404d48f2f7870367d3a0a4e5f7f96304948475e087dd90d4b23cf82d1d273e31e06a5b71be06cb2f66bb28f967f70743014a5f06d1db5b14765c
pt-BR/chrome.admlChangedc041a9a24dabc38dc5e01f35919fa7431ac50b55e5ece6c7a31cc75b737f8510302bd6d30cd48ef232597d5479a2e9f8d05f3a0086a3ea852cc8e1bda183e830
ru-RU/chrome.admlChanged701af8d806bf1a4ba863661419ad9a4c72592e4451669576ac81f571709177575ce14e7b3415b236884d89714ce5d0f060ace73f69ebb6f97c2a983483b84f1a
th-TH/chrome.admlChanged385c6ff0f4415e2885891cf196b76550f54c918c1cb42d5619e5387671499c30af4a05e73895afff300a562f51a9969f5e102fd1685bd2a25617b5f61fcac4e2
tr-TR/chrome.admlChanged5ad708877dda731e7074d123bb2d1ac6896a3199a78f4532a424de5e260c8db6e0c1a63d695ec74271d2c1f0ad8f0c2662df957202b8ae5d10fed07ba9a5ce89
uk-UA/chrome.admlChanged542d6811aa84f8761116e901366ddaa6d7a54d632e64617972e77abdfc4429e59f30c928e470f495dcd373a97ac00f24e74d3be6b92a8beefa63261d255011d8
vi-VN/chrome.admlChanged0ea3b5c698ce8b75b0a1a37dbb115a649898c3b82513a51847fc3655587e8b18d029776c6ef90b86c5ee0c0eee3863220f417e16993a379c3127b3569c6d9b85
zh-CN/chrome.admlChangedb36376822f87ff898ca567d01c908b8cb032a7277f8e1d526eb5db37abaaaef8ef4358288e990ab106b1bbf56c5d0464f6b79a5c14111d71cc55e005a8ce8346
zh-TW/chrome.admlChangeda029993a4e21b38a39457b80fc5a74fbe797a6535d12fdd1b776481afc1b332f6db7803609242c26371ab8122ef188c0d469b21cf5e92abf176829e855c50bdd
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 13:23 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current