Get In Touch
Helping customers further secure their on-premises data centers and IaaS deployments is an interesting new use case for our Enterprise Threat Protector service.
As the world shifts to an increasingly virtual environment, Akamai continues to be at the forefront of helping customers enable workforce productivity with Akamai's Enterprise Application Access and Enterprise Threat Protector. From our detailed offer to our recent Edge Live Virtual Summit, where Akamai executives spoke about enabling a remote workforce on our platform, we have shared programs and processes around ensuring business continuity. This continues to be a concern
The need for companies to quickly enable remote access to business-critical applications was highlighted in a recent Akamai blog -- Enabling Business Continuity in an Uncertain Global Environment.
Today, Akamai announced that it has added secure web gateway (SWG) capabilities to its Enterprise Threat Protector (ETP) service to help enterprises further accelerate their transformation to a Zero Trust security architecture. So what are the SWG enhancements and what benefits will these deliver for Akamai customers?
In the second part of this blog, I covered how HTTPS web content inspection is provided in Akamai's Enterprise Threat Protector (ETP) service using ETP proxy. In this final blog post I want to provide information about how Akamai generates, distributes and controls access to private keys including TLS certificates.
In the first blog post I covered why HTTPS web traffic has grown to unprecedented levels, provided a TLS primer and looked at the basic concept of intercepting and inspecting HTTPS web traffic with Man-In-The-Middle techniques (MITM). In the second part, I will dive a bit deeper into how the TLS MITM capability has been implemented in Akamai's Enterprise Threat Protector (ETP) service.
In this series of blogs I'm going to talk about how the continued move towards all web traffic being encrypted has impacted enterprise security. In this blog I'm going to focus on the basics - what is encrypted web traffic and how can you proactively control this.
In the early 2000s, security was mostly focused on perimeter separation between the trusted corporate internal network and the untrusted everything else. Separation was very clear, as most corporate applications were inside the perimeter and users were office based, with a very low amount of remote working.
Recursive DNS communications are normally unencrypted between a client and a resolver. In an effort to improve user privacy and address security concerns, Mozilla announced it would begin enabling DNS over HTTPS (DoH) by default in its Firefox browser. However, Mozilla recognized it would be necessary in some cases for enterprises to be able to inspect DNS traffic to enforce security controls. Consequently, Firefox also supports a "Network Signal" that,