{"id":6563,"date":"2026-10-19T12:07:05","date_gmt":"2026-10-19T09:07:05","guid":{"rendered":"https:\/\/support.withsecure.com\/?page_id=6563"},"modified":"2026-10-19T12:07:05","modified_gmt":"2026-10-19T09:07:05","slug":"general","status":"publish","type":"page","link":"https:\/\/support.withsecure.com\/en\/announcements\/products\/general\/","title":{"rendered":"General WithSecure Announcements"},"content":{"rendered":"<section\n    class=\"wp-block-support-banner edwp-block wp-block-support-banner--bg-light-gray layout--spacing-xxxl-top layout--spacing-xxxl-bottom\"\n    >\n            <div class=\"wp-block-support-banner__container\">\n        <div class=\"wp-block-support-banner__content-wrapper\">\n                        <div class=\"wp-component-content wp-component-content--default wp-block-support-banner__content\">\n            <h2 class=\"wp-component-heading text--h2 wp-component-content__title\">\n    Announcements<\/h2>                    <div class=\"wp-component-content__inner\">\n                                    <div class=\"wp-component-content__content wysiwyg\">\n                        <div class=\"wp-component-paragraph \">\n    <h4>General WithSecure Announcements<\/h4>\n<\/div>\n                    <\/div>\n                                                            <\/div>\n                <\/div>                            <div class=\"wp-block-support-banner__searchbar\">\n                    <div class=\"addsearch-standalone-searchbar-container\" data-addsearch-results-url=\"\/en\/search\"><\/div>\n                <\/div>\n                                <\/div>\n    <\/div>\n<\/section>\n\n\n<section\n    class=\"wp-block-content-list edwp-block layout--spacing-l-top layout--spacing-l-bottom\"\n    >\n    <div class=\"wp-block-content-list__container\">\n        \n        <div class=\"wp-block-content-list__main\">\n                    <ul class=\"wp-block-content-list__list\">\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2026-04-16T14:17:04+00:00\">April 16, 2026<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/cve-2026-40175-for-axios-javascript-library-2\/\">\n                <p class=\"wp-block-content-list__title\">CVE-2026-40175 for Axios JavaScript library<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <h4 data-id=\"what-is-axios\"><strong>What is Axios?<\/strong><\/h4>\n<p>Axios is a JavaScript library intended to ease interaction with internet HTTP services. It is used by some organizations to simplify their codebase compared to using standard browser functionality.<\/p>\n<h4 data-id=\"what-is-the-vulnerability\"><strong>What is the vulnerability?<\/strong><\/h4>\n<p>Prior to version 1.15.0, the Axios library is vulnerable to a specific &#8220;Gadget&#8221; attack chain that allows Prototype Pollution in any third-party dependency to be escalated into Remote Code Execution (RCE) or Full Cloud Compromise (via AWS IMDSv2 bypass).<\/p>\n<p>Ref: <a href=\"https:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fnvd.nist.gov%2Fvuln%2Fdetail%2FCVE-2026-40175\" rel=\"nofollow noopener ugc\" target=\"_blank\">https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2026-40175<\/a><\/p>\n<h4 data-id=\"has-the-vulnerability-been-fixed\"><strong>Has the vulnerability been fixed?<\/strong><\/h4>\n<p>This vulnerability has been fixed in 1.15.0.<\/p>\n<h4 data-id=\"what-are-withsecure-s-recommendations-for-partners-and-customers\"><strong>What are WithSecure\u2019s recommendations for partners and customers?<\/strong><\/h4>\n<p>We recommend partners and customers who use Axios act immediately to ensure their systems are not vulnerable.<\/p>\n<p><strong>WithSecure Exposure Management<\/strong> can detect and notify partners and customers that they have a vulnerable version.<\/p>\n<p>Detection for vulnerable versions is available in unauthenticated scanning, and we are investigating the possibility to detect them on hosts via authenticated scans<\/p>\n<h4 data-id=\"what-is-the-status-of-withsecure-systems-in-relation-to-this-vulnerability\"><strong>What is the status of WithSecure systems in relation to this vulnerability?<\/strong><\/h4>\n<p>WithSecure has thoroughly checked its own systems, and has confirmed that all services using Axios are using the latest version which is not vulnerable.<\/p>\n<h4 data-id=\"are-any-withsecure-products-affected\"><strong>Are any WithSecure products affected?<\/strong><\/h4>\n<p>WithSecure Policy Manager does contain a vulnerable version of the Axios library, and we have created a hotfix for this issue.  We advise all our Business Suite partners and customers to apply this hotfix at the earliest opportunity.<\/p>\n<p>The risk can further be mitigated by ensuring that Policy Manager\u2019s Web Reporting interface is not accessible from the internet. This can be done with external firewall configurations.<\/p>\n<p>The hotfix can be downloaded from the <a href=\"https:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fsupport.withsecure.com%2Fen%2Fsupport%2Fproduct-support%2Fbusiness-suite%2Fpolicy-manager%23download\" target=\"_blank\" rel=\"nofollow noopener ugc\">WithSecure Download Center<\/a>.<\/p>\n<\/div>\n                <\/details>\n                    <\/li>\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2024-09-12T06:09:08+00:00\">September 12, 2024<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/major-capricorn-update-for-endpoint-protection\/\">\n                <p class=\"wp-block-content-list__title\">Major Capricorn update for Endpoint Protection<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <p><strong>UPDATE: 2024-09-25<\/strong>: This upgrade has now been published as <strong>WithSecure Capricorn Engine (2024-09-25_04).<\/strong> Please note that due to the way clients check for updates, some customers will not receive this until slightly later in the day. Subsequent Capricorn updates will also include this change.<\/p>\n<p><strong>UPDATE 2024-09-24:<\/strong> We anticipate that this update will start being delivered to our customers from 9.00 UTC 25.09.2024, but it is unfortunately not possible to give an exact time due to the way client installations check for updates. The update size will be ~39MB, and not the 42,6MB announced earlier<\/p>\n<p>We plan to release a major Capricorn database update on September 24th, 2024.<\/p>\n<h4 data-id=\"what-does-this-update-mean\"><strong>What does this update mean?<\/strong><\/h4>\n<p>This update signifies that all Withsecure Endpoint products &#8211; across Windows, Mac, and Linux platforms (those utilizing the Capricorn engine) will now download a larger update package of approximately 42,6 MB, compared to the usual 5MB.<\/p>\n<p>For customers managing large environments or dealing with bandwidth constraints, this information could be particularly relevant. Additionally, users can expect improved initialization times and reduced memory consumption as part of the update\u2019s benefits.<\/p>\n<p>The update is<strong> provided automatically<\/strong> and does not require any additional configuration.<\/p>\n<ul>\n<li>The release time will be announced 24 hours in advance through our community channels. <\/li>\n<li>Updates containing this release will start with &#8220;WithSecure Capricorn Engine (2024-09-xx-xx)\u201d<\/li>\n<li>Users of WithSecure Elements EPP may wish to consider taking the Elements Connector into use, to help reduce internet access, if they have several deployed endpoints. You can find more details of how to deploy this at <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fuserguides%2Fdata%2Fpdf%2Fws_elements_connector_eng.pdf\" rel=\"nofollow noopener ugc\" target=\"_blank\">https:\/\/www.withsecure.com\/userguides\/data\/pdf\/ws_elements_connector_eng.pdf<\/a> <\/li>\n<\/ul>\n<\/div>\n                <\/details>\n                    <\/li>\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2024-09-05T06:54:43+00:00\">September 5, 2024<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/important-reminder-all-protection-for-f-secure-branded-b2b-products-ends-completely-on-december-31st-2024\/\">\n                <p class=\"wp-block-content-list__title\">Important Reminder: ALL Protection for F-Secure branded B2B products ends completely on December 31st 2024<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <p>If you are using an <strong>F-Secure<\/strong> branded B2B product, please read on, as <strong>this article contains information you need to ensure protection and functionality<\/strong> continues in 2025.<\/p>\n<p>We have previously communicated to our partners and end customers that support <strong>for F-Secure branded<\/strong> on-premises products will end completely in late 2024. This information was also published <a href=\"https:\/\/community.withsecure.com\/en\/kb\/articles\/31335-important-information-end-of-support-for-old-versions-of-on-premises-products\" target=\"_blank\" rel=\"nofollow noopener ugc\">in this article<\/a>.<\/p>\n<p>As part of infrastructure changes related to our separation from F-Secure, the update servers for the old products will cease to exist. <strong>Support ends<\/strong> for these older products at the end of September in most cases, but we will endeavour to continue providing protection updates for these until the end of the year.<\/p>\n<p>As we roll into 2025, it will be <strong>IMPOSSIBLE<\/strong> for us to offer any support for these products, as we will have no possibility to provide updates to these products. <strong>The products will stop receiving updates, and will no longer provide protection<\/strong>.  To ensure continued delivery of updates, and therefore protection of your systems, <strong>it is vitally important that you update systems before the deadline<\/strong>.<\/p>\n<p>In particular, this end of support reminder affects the following products, <strong>including<\/strong> Premium versions. You can find the minimum supported version.<\/p>\n<div class=\"tableWrapper\">\n<table>\n<thead>\n<tr>\n<th>\n<p><strong>Legacy F-Secure Product<\/strong><\/p>\n<\/th>\n<th>\n<p><strong>Replacement WithSecure Product<\/strong><\/p>\n<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\n<p>F-Secure Business Suite<\/p>\n<\/td>\n<td>\n<p>WithSecure Business Suite 16 series<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Client Security<\/p>\n<\/td>\n<td>\n<p>WithSecure Client Security 16.x<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Client Security for Mac  <\/p>\n<\/td>\n<td>\n<p>WithSecure Client Security for Mac 16.x<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Server Security<\/p>\n<\/td>\n<td>\n<p>WithSecure Server Security 16.x<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Policy Manager &amp; Policy Manager Proxy (also Linux versions)<\/p>\n<\/td>\n<td>\n<p>WithSecure Policy Manager 16.x<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Email and Server Security<\/p>\n<\/td>\n<td>\n<p>WithSecure Email and Server Security 16.x<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Linux Security<\/p>\n<\/td>\n<td>\n<p>WithSecure Linux  Security  12.0.482<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<p>F-Secure Atlant<\/p>\n<\/td>\n<td>\n<p>WithSecure Atlant  1.0.319<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Replacement WithSecure branded versions are available for all of these products at our <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fsupport%2Fdownload\" target=\"_blank\" rel=\"nofollow noopener ugc\">download center<\/a>. <\/p>\n<p><strong>Please note<\/strong> that some service network addresses have changed for these WithSecure-branded products, and our customers need to ensure that connectivity is allowed to the new addresses. You can find <a href=\"https:\/\/community.withsecure.com\/en\/kb\/articles\/31208-network-addresses-for-withsecure-on-premise-products\" rel=\"nofollow noopener ugc\" target=\"_blank\">more information at the dedicated article<\/a><\/p>\n<p>Partners and customers have already received keycodes for the new versions where applicable.<\/p>\n<p>On-premises products that are branded as WithSecure, and all WithSecure Elements products, continue to be supported <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fsupport%2Fproduct-lifecycle-announcements\" rel=\"nofollow noopener ugc\" target=\"_blank\">until their published end of life dates<\/a>.<\/p>\n<\/div>\n                <\/details>\n                    <\/li>\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2024-05-02T06:32:45+00:00\">May 2, 2024<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/withsecure-is-refreshing-its-terms-of-use-for-our-products-and-services\/\">\n                <p class=\"wp-block-content-list__title\">WithSecure\u2122 is refreshing its Terms of Use for our products and services<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <p>From time to time, WithSecure updates its <strong>Terms of Use<\/strong> for our products and services. These <strong>Terms of Use<\/strong> have earlier also been named \u201c<strong>End User License Terms<\/strong>\u201d or \u201c<strong>End User License Agreement<\/strong>\u201d.<\/p>\n<h4 data-id=\"why-are-we-changing-the-terms-of-use\">Why are we changing the terms of use?<\/h4>\n<p>As we have also stated in our terms of use, our products and services are improved from time to time and therefore the terms of use also need updating from time to time.<\/p>\n<p>Mainly the changes for this version are stylistic and minor. The updated terms of use are materially similar as in the previous version.<\/p>\n<h4 data-id=\"when-are-these-being-changed\">When are these being changed?<\/h4>\n<p>The new terms will come into effect from <strong>1 June 2024<\/strong>, with endpoint clients being updated to use them soon afterwards. Until then, <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fabout-us%2Flegal%2Fterms\" rel=\"nofollow noopener ugc\" target=\"_blank\">the existing terms of use apply<\/a>.<\/p>\n<h4 data-id=\"what-do-i-need-to-do-as-a-partner-or-end-customer\">What do I need to do as a Partner or End-Customer?<\/h4>\n<p>In short, nothing, but if you wish<a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fcontent%2Fdam%2Fwith-secure%2Fen%2Fresources%2Flegal%2FWithSecure_Terms_of_Use_May_2024.pdf\" rel=\"nofollow noopener ugc\" target=\"_blank\"> you can review the updated terms<\/a> (in PDF format). These preview terms are currently only available in English, but will be available in other languages when the new terms come into use.<\/p>\n<p>The updated terms will automatically be applied from 1 June 2024 onwards.<\/p>\n<p><strong>Note<\/strong>: Continued use of WithSecure\u2122 products and services means acceptance of these new terms.<\/p>\n<\/div>\n                <\/details>\n                    <\/li>\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2024-03-27T09:12:52+00:00\">March 27, 2024<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/support-status-windows-8-8-1\/\">\n                <p class=\"wp-block-content-list__title\">Support Status: Windows 8\/8.1<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <p>As Microsoft Extended Support for all Windows 8\/8.1 versions ended during 2023, WithSecure will stop supporting these versions of Microsoft Windows from 31st March 2024.<\/p>\n<p>This applies to all WithSecure products. This change does not affect the overall support for those products when they are used on supported operating systems.<\/p>\n<p>Customers who are using these versions of Microsoft Windows are advised to upgrade them, or replace the devices, so that they can use versions of Windows that are supported by Microsoft. Both Microsoft and WithSecure strongly recommend that customers should only use supported versions of products, to maintain security and protection.<\/p>\n<p>For users of WithSecure Elements, the \u201cDevices\u201d view can show unsupported operating systems, if the \u201cOS End of Life\u201d field is enabled.<\/p>\n<\/div>\n                <\/details>\n                    <\/li>\n            <li class=\"wp-block-content-list__item\">\n                            <time class=\"wp-block-content-list__updated\" datetime=\"2024-02-19T13:36:47+00:00\">February 19, 2024<\/time>\n            \n            <a class=\"wp-block-content-list__link\" href=\"https:\/\/support.withsecure.com\/en\/announcements\/network-addresses-for-withsecure-countercept\/\">\n                <p class=\"wp-block-content-list__title\">Network Addresses for WithSecure Countercept<\/p>\n            <\/a>\n\n            \n                            <details class=\"wp-block-content-list__details\">\n                    <summary class=\"wp-block-content-list__summary\">Read more<\/summary>\n                    <div class=\"wp-component-paragraph wp-block-content-list__body\">\n    <p>In May 2024 we are releasing new versions of Countercept Agents for Windows, Linux and Mac platforms. Managed clients will get all these changes automatically. A little later we will publish new release groups to switch clients using managed updates in collaboration with the WithSecure Engagement team.After the upgrade new versions of Countercept Agents will start using new addresses. <\/p>\n<p>For many customers, WithSecure products will function correctly without needing to know which servers the products connect to.<\/p>\n<p>However, some administrators tightly control which network addresses they allow their clients to connect to (\u201cEgress control\u201d or \u201coutbound connections\u201d), and it is\u00a0<strong>mandatory<\/strong>\u00a0that they allow connections to the following addresses. WithSecure cannot guarantee the functionality of the products if access to these addresses is blocked.<\/p>\n<p><strong>The product may not function correctly if access to these network addresses is not allowed.<\/strong><\/p>\n<p>Please note that all the following require outbound connections to TCP\/443 unless otherwise stated.<\/p>\n<p>Additionally, any products listed in this document also includes F-Secure branded versions of the same products.<\/p>\n<h4 data-id=\"recommendations\">Recommendations<\/h4>\n<p>WithSecure recommends, where possible, that administrators allow outbound access to all address under the withsecure.com and fsapi.com domains. We do appreciate that this is not always possible due to firewall configuration limitations, or even from an operational perspective, so we are publishing an explicit list of server addresses.<\/p>\n<p>Please note that\u00a0<strong>we do not guarantee<\/strong>\u00a0this list of addresses is complete or will stay unchanged, so we strongly recommend bookmarking these articles for future reference. We will update these articles whenever needed.<\/p>\n<h4 data-id=\"withsecure-countercept\">WithSecure Countercept<\/h4>\n<h5 data-id=\"new-addresses\">New addresses <\/h5>\n<p>After the upgrade new versions of Countercept Agents will start using new addresses. <\/p>\n<p>Please note that all the following services require outbound connections to TCP\/443 unless otherwise stated. <\/p>\n<p>In addition, the use of an asterisk (*) below means that all hosts under that subdomain should be allowed (wildcard allow).<\/p>\n<ul>\n<li>*.fsapi.com (also port 80)<\/li>\n<li>ac3ujg1ortm4c-ats.iot.eu-west-1.amazonaws.com (also port 8883, if the network includes Windows 7, Windows Server 2008 R2, or Windows Server 2012 endpoints)<\/li>\n<li>c3hquxgihnj763.credentials.iot.eu-west-1.amazonaws.com<\/li>\n<li>ew1-famp-prd-system-transfer.s3.eu-west-1.amazonaws.com<\/li>\n<li>*.digicert.com<\/li>\n<\/ul>\n<p>If you are unable to allowlist wildcard, either from a technical or operational standpoint, please contact your WithSecure Engagement Manager who will be pleased to advise you further.<\/p>\n<h4 data-id=\"connectivity-checker\">Connectivity Checker<\/h4>\n<p>We also provide tools that can assist you in checking whether your firewall allows the needed external connections.<\/p>\n<h5 data-id=\"for-microsoft-windows\"><strong>For Microsoft Windows<\/strong><\/h5>\n<p>Download the Connectivity Tool from WithSecure\u2122 Support Tools library. Support Tools library, or using direct download link <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdownload.withsecure.com%2Fconnectivitytool%2FConnectionChecker.exe\" rel=\"nofollow noopener ugc\" target=\"_blank\">https:\/\/download.withsecure.com\/connectivitytool\/ConnectionChecker.exe<\/a>  <\/p>\n<p>Run the tool on the machine where the installation is being attempted by double clicking on the tool through Windows Explorer. The tool will prompt for administrator credentials when it runs.  <\/p>\n<p>Select MDR product from the list. <\/p>\n<p>If a proxy is going to be used for the installation, it must be defined when prompted. If a proxy is not going to be used, leave the proxy settings empty. <\/p>\n<h5 data-id=\"for-linux-and-mac\"><strong>For Linux and Mac<\/strong><\/h5>\n<p>Download the Connectivity Checker tool with the direct link  <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdownload.withsecure.com%2Fconnectivitytool%2Fwsconnectionchecker.zip\" rel=\"nofollow noopener ugc\" target=\"_blank\">https:\/\/download.withsecure.com\/connectivitytool\/wsconnectionchecker.zip<\/a> <\/p>\n<p>Unpack the tool with: unzip wsconnectionchecker.zip <\/p>\n<p>Set execution bit if needed:<\/p>\n<p><code class=\"code codeInline\" spellcheck=\"false\" tabindex=\"0\">sudo chmod +rwx wsconnectionchecker <\/code><\/p>\n<p>Run the tool in Linux or Mac mode depending on your needs. If a proxy is going to be used for the installation, it must be defined with the -p parameter. If a proxy is not going to be used use parameter \u2018-d\u2019 instead, for example:<\/p>\n<p><code class=\"code codeInline\" spellcheck=\"false\" tabindex=\"0\">.\\wsconnectionchecker -o linux -p http:\/\/myproxy.com:3128<\/code> <\/p>\n<p>or <\/p>\n<p><code class=\"code codeInline\" spellcheck=\"false\" tabindex=\"0\">.\\wsconnectionchecker -o mac -d <\/code><\/p>\n<\/div>\n                <\/details>\n                    <\/li>\n    <\/ul>\n\n                            <\/div>\n    <\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":0,"featured_media":0,"parent":6560,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-6563","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/pages\/6563","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/comments?post=6563"}],"version-history":[{"count":1,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/pages\/6563\/revisions"}],"predecessor-version":[{"id":6568,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/pages\/6563\/revisions\/6568"}],"up":[{"embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/pages\/6560"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=6563"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}