Symantec Protection Engine for Cloud Services on Linux

I tried using Symantec Protection Engine  on AWS  cloud and have constructed some implementations. It was purchased through AWS  marketplace.

What I appreciate in Symantec Protection Engine  is the Virtual Policy Manager (VPM) and the Application Name feature, which are really effective. The simple match request URL features are basic but highly efficient. The header and request header controls represent a significant improvement compared to other vendors. The categorization and custom categorization features are also excellent. These four elements represent the strongest parts of Symantec Protection Engine.

The seamless integration of Symantec Protection Engine benefits my IT infrastructure, although the Symantec proxy only works with Symantec solutions such as DLP  or Content Analyst. Sometimes it works with accounts like Okta or SAML, but third-party solutions usually do not integrate well with Symantec. Only Symantec products work effectively with Symantec.

The high-performance scanning impact on my organization includes improved policies that allow specific redirection to people. The policies are very detailed, enabling me to specify which person receives which policy and how to control company users through these policies. This represents a significant improvement compared to other proxies.

Symantec Protection Engine has fewer issues during installations. However, some customers find it confusing to distinguish between the normal proxy and the web proxy because Symantec Protection Engine only controls port 80 and 443, which are HTTP and HTTPS. Because of this limitation, applications or browsers that are not supported sometimes may not work, and certain government sites or other sites may not function. Other national proxies made in Korea and other vendors support all ports.

Complexities can arise when customers use the proxy. The Web UI is good and has many improvements, but there are still some things that need enhancement.

Price is a significant area for improvement. The pricing is quite expensive, and it is particularly high for regular customers. Many customers are considering other vendors because the price is too high.

The Symantec proxy limitation to work only with Symantec products represents another weakness. While it sometimes works with accounts like Okta or SAML, third-party solutions usually do not integrate properly with Symantec. Only Symantec products work with Symantec.

It is difficult to assess whether it remains beneficial to use Symantec Protection Engine in terms of costs because the price is very high. Although the product has benefits, the pricing is extremely high. Symantec Protection Engine works very well for huge companies, but when company size is large, network size is also large, requiring a bigger proxy and significantly higher pricing. The cost multiplies based on scale, making it highly effective for Symantec but at multiple times the standard price.

I have been working with Symantec Protection Engine for almost three to four years.

The technical support of Symantec deserves a 10 because they provide extensive support.

Positive

The deployment timeframe depends on the size of the implementation, but deployment may require around one hour. I can complete the deployment within one hour since I personally participate in the deployment process. The installation is straightforward, but when the company is large with substantial size and many policies, stabilization may take additional time. However, the deployment itself takes approximately one hour because it is very simple to deploy and install.

I use policy management capabilities with the Visual Policy Manager. The impact of policy management on my security and my customers' security allows me to install policies for specific options, a specific person, or a specific group. The policy layers are very detailed, which I appreciated greatly.

The effectiveness of Symantec Protection Engine's Threat Intelligence Network in protecting against evolving threats is beneficial for the proxy because it has a threat risk level. Symantec officially supports levels 1 through 10, and I would consider levels 8 through 10 acceptable, while levels 5 through 7 are warnings. This system is helpful for customers. In threat protection, the categorization is excellent because Symantec provides strong support for it. Symantec effectively supports categorization, specifying which sites are threat sites, and when I set a suspicious category to deny, it functions effectively.

I do not use the real-time content scanning feature with Symantec Protection Engine; I only use the web proxy structure.

My overall rating for this product is 7.

My main use case for Symantec Protection Engine  in our organization involves both scanning and protection. We have nearly 200 servers in our environment with the Symantec agent installed. I use Symantec Protection Engine  daily as part of our business-as-usual activities, primarily for real-time scanning and protection across SharePoint , web applications, and servers.

Scanning is performed online during file transfers, with optional scheduled scans to catch any missed items. The incident response team at Kyndryl  also leverages this tool, integrating it with other platforms to forward logs to our SOC monitoring team.

Symantec Protection Engine's been a game-changer for us at Kantar—blocks like 80-85% of file-based threats right at the gateway before they hit our 200 servers, cutting down endpoint incidents big time.

The main win is that real-time ICAP scans on NAS  and SharePoint  uploads quarantine ransomware or phishing docs instantly with ML, so instead of 20+ CrowdStrike remediations a week, we're down to 8-10. SOC shifts save 1-2 hours daily on handovers thanks to the central dashboard and syslog feeds to ServiceNow , freeing us up for phishing deep dives with Trend Micro or CySA+ studying.

Also slashed MTTR by half on server threats 90 mins vs 4 hours by auto-exporting hashes for L3 analysis.

The best features of Symantec Protection Engine include machine learning, file reputation, and real-time scanning. It efficiently handles heavy loads through ICAP and cloud-based processing, reducing the burden on endpoints compared to Trend Micro and other endpoint security solutions. Its centralized control is also noteworthy.

Through machine learning, it detects both known and unknown malware and malicious URLs, in addition to performing signature-based scans that assist SOC teams in analysis. The solution is highly effective in leveraging both machine learning and file reputation. Regarding centralized control, it offers a unified management console for policy deployment and provides real-time visibility through dashboards, helping save significant administrative time.

Symantec Protection Engine has had a positive impact on our organization by enhancing our overall security posture. It effectively blocks a high volume of file-based threats across more than 200 servers, saves SOC analysts time in endpoint remediation, and streamlines compliance processes. It further strengthens security through real-time scanning and machine learning-based quarantine, blocking phishing payloads in SharePoint uploads before they reach endpoints, thereby reducing incidents by 30–40% compared to signature-only tools.

To improve Symantec Protection Engine, I suggest simplifying its integration with other tools, as it is more complex compared to Trend Micro and CrowdStrike. Making the integration process easier would be highly beneficial.

I have used Symantec Protection Engine for approximately two to three years.

The reduction has positively impacted our team's workload, decreasing ticket volume by approximately 30 to 40 percent. This means less work for our SOC team, as they now receive fewer tickets. From a cost and resource perspective, this change has been beneficial.

In my experience, Symantec Protection Engine offers efficient scalability, allowing the easy addition of multiple servers. While the on-premises setup depends on the capacity of the installed servers, in AWS  we can easily scale from 200 to 500 instances—and sometimes even to thousands daily—through ICAP load-balancing mirroring.

I have interacted with the customer support team for Symantec Protection Engine, and it was excellent to work with them. They provided solutions that were very effective.

Positive

I have previously worked with multiple tools before using Symantec Protection Engine, including Trend Micro, CrowdStrike, and Microsoft Defender. I used these tools in different projects, alongside Symantec Protection Engine.

Straightforward

consultant

Pricing for Symantec Protection Engine was decent.

I didn’t evaluate many other options before choosing Symantec Protection Engine, as it was already part of the project when I joined, so I couldn’t change it. However, I would recommend exploring other tools when the renewal opportunity arises.

Symantec Protection Engine scans incoming content and occasionally raises alerts if it detects anything concerning. It is currently deployed on-premises in our environment. I recommend others consider using Symantec Protection Engine because it is cost-effective. 

However, I suggest opting for the cloud version instead of on-premises or hybrid deployments, as the cloud offers better scalability and easier troubleshooting. Overall, I would rate this product 8 out of 10.