What is your primary use case for Cisco Secure Email?

The primary use case for Cisco Secure Email is for email security. It is used in scenarios similar to Fortinet, focusing on email security and integrating with Cisco Firewalls.

I use Cisco Secure Email mainly as a email security gateway, including internal email distribution.

I use the solution in my company for email security. The tool is the email gateway we use for email security in our company. Cisco Secure Email acts as the first level of defense in our company's email security flow. When an email arrives, it first arrives in Cisco Secure Email Gateway, after which it gets filtered there, and then it passes through our Microsoft 365 Defender.

My company operates as a service provider, and we use Cisco Secure Email so that we can secure the endpoints, systems, and emails in our data center.

I use the solution for email security.

We use it primarily for filtering both internal and external messages, especially within our Office 365 environment. It serves as our main filtering solution.

Our customers use the solution as an email security tool.

We use Cisco email security against threats such as phishing and malware and block weaponized URLs. Cisco provides a cloud solution, along with the appliance, and a hybrid solution is also there. We deploy the solution as per the customer's requirements.

We have a number of different types of customers and organizations who need to secure their environment. These range from healthcare professionals to financial organizations to very small organizations. They have a number of security requirements, whether it's just to secure the actual environment where they're working and also to provide additional services, such as VPNs and remote access for their remote workers. Most of the customers that I work with tend to be on-prem, and a lot of them go with the centralized management system, FMC, purely because it has larger memory and larger hard disk space, and it can hold reports for a much longer period of time. Also, as their network infrastructure scales, FMC can manage more and more of their devices, and they're not having to manage individual devices. It's all centralized for them.

We use Cisco Secure Email for email security.

The product is used for email security. We have around forty boxes of Cisco and cater to around four million users.

Originally, Cisco Secure Email was primarily intended to combat spam. The day we installed it, we immediately noticed a significant difference. Since then, it has proven to be one of the best investments we have made in the fight against spam. However, its functionality has expanded beyond spam prevention. It now includes features such as Data Loss Prevention, quarantining of malicious attachments, compliance with workplace policies, and assistance in battling against phishing attempts.

We have it for email security. We use it for some security features to set up emails.

I work at S21sec, which is a partner of Cisco in Portugal. We do integration of different Cisco solutions for our customers. Nowadays, we mostly do integration of Cisco cloud solutions for customers. Cisco Secure Email is the solution that we deploy for customers in Portugal mostly as a backup of an existing solution such as Office 365 because it guarantees that the customer never falls out of options if the main product has some problem. If they rely on having an email solution that cannot fail, that's an excellent option for them to have in place. It's the oldest solution that we deploy for customers in Portugal. It has a very nice history and very good quality. It's perceived by our customers as an email solution that functions all the time.

We started using Cisco Secure Email because we had a lot of junk emails, phishing, and things like that. We wanted to secure the email sites for the end users.

It is like a gateway for email. They receive all your email traffic. They send over your email traffic, and it is the first incoming point and the last outgoing point. They deliver the traffic to the destination. Whatever it is, you want to be informed of what is happening. Depending on the site's deployment, if you have a single device, then you have all the information on the device. And if you have several devices, you have all the information on every single device for each device. However, for consolidation, you need another device called Security Management Appliance (SMA). It has no real interaction with other stuff. It does not interact with a gateway beyond the networking level. You have a router and that router provides IP addresses for a switch, etc. You don't have to integrate Cisco Secure Email with something specific since it is standalone and only requires basic essential networking. You can integrate it with a firewall, like ASA, but that firewall has to allow traffic. To do that, you would open port 25. It is available to be deployed as on-premises, on the cloud, and hybrid cloud.

We migrated from Cisco ESA to Cisco CES, we went from the on-premise solution to the cloud solution. Our primary use case is for email security. Every email is scanned by an antivirus engine and every attachment is also sandboxed before it gets back to the real person. This is an additional Cisco CES module. On top of this module, we have also subscribed for the Cisco Cloud Secure Email Encryption Service (CRES). Our other use cases are all about the functionality of the Cisco Email. We are using it as a relaying system for incoming and outcoming mail. External exposed webservices are using the Cisco CES in order to send mails out as our domains. Another feature we use is the possibility to combine the Cisco CRES together with Cisco CES. All our documents are labelled and are obliged to be sent either through TLS (encrypted channel) or either through Cisco CRES (encrypted mail) for GDPR-compliancy. If the destination domain doesn't support TLS, it is sent by Cisco CRES, otherwise we use TLS. This conditional check isn't (yet) available at Microsoft.

It is our email gateway. We have the Exchange Servers, but the Exchange Servers don't relay directly with the internet. We have ESA in-between, and every incoming and outgoing email must pass through ESA before it gets to the internet. We are using Email Security Appliance C690, and we have three of them in a cluster. They are on-premise. We have decided not to go to the cloud. It is primarily because most of our clients are government agencies and the government, and they have this suspicion about the cloud. So, right now, we are still on-premise. Currently, we are on version 13.8. There is a newer version, but we are yet to migrate to that version.

All of our inbound and outbound emails flow through the CES environment and we leverage it for spam filtering, phishing filtering, malicious URL detection, attachment scanning, and data leak protection. It basically covers all of the security layers for email.

We are an internet service provider with over 1,000 customers. All our customers need a reliable solution for email security and this solution from Cisco helps us to implement the customers' needs and to offer the security the customers want. We are using all the appliances on premises. They are virtual appliances only. We are not using the cloud because we own our data center.

We are using it for our email gateway security for all our inbound and outbound email. We use a lot of the URL filtering and spam filtering as well as the dictionaries, e.g., if they try to spoof employee names.

It is used as the primary perimeter gateway for our organization before you can access our environment. Being hosted with Cisco, it goes through Cisco Secure Email Cloud Gateway. Spam, marketing, malicious or virus-enabled emails are not delivered to us 90 to 91 percent of the time because they are stopped external to the organization. That is a massive win for us. We don't have to worry about having to deal with all those emails going through our email servers.

The main use case is simply as a point of contact for all the emails to go through first, before they ever get into the Office 365 environment, so they can be scanned and checked for malware and spam, all before Office 365 even sees it. We're currently on version 12. Our instance is in the cloud and we don't actually upgrade it, they do it for us. It should be upgraded to 13 in the next month or two.

I have experience as an SE for IronPort as well as a private consultant. I have used this solution in multiple environments.

It is an anti-spam solution, and we primarily use it for email anti-spam. It removes the spam emails, and we have our own manual filters to remove unnecessary or unwanted emails. So, it is working just fine. We have been using the solution for more than three years. We started on version 9 and are currently on version 11.1.

We have around 500 to 600 users and we use it for services like Anti-Spam, Advanced Malware Protection (AMP), and scanning. We are also using also multiple content filters, and it's working pretty well for us. In combination with Cisco Secure Email Gateway, we are using Trend Micro.

We use it to secure our email system, to cut down on all the bad emails that we would otherwise receive. The reason for implementing the product was the huge increase in spam and junk mail which occurred when we were adopting these devices. There have been some changes in the way that email is delivered since then, and one or two of the major spam sources have been taken down or prosecuted or jailed. Today, we have less blanket-spam, but we have more targeted phishing emails or spear phishing. The combination of emails with links that encourage users to give away their user login information can cause problems. When someone's account is compromised it can result in access to our global address list and access to emails that the compromised user may have sent. Therefore, they have details of the format and the style emails that our company uses. We have communication threads that they can take advantage of because they can inject their fake emails into an existing communication thread and try to fool a supplier or client into giving more information or, worst-case, giving money to the wrong person.

Protection against external email threats is our primary use case.

It's our primary enterprise email gateway. It's the first stop for edge email security.

We used Cisco Secure Email Gateway to filter spam. My overall experience with Cisco Secure Email Gateway was pretty good. No major issues were reported in my time. It worked fine for me.

The primary use case was for email security and load balancing between Exchange mail servers.

My primary use case was email security, to protect against phishing mails, spam, malware, and viruses.

Our main deployment is for a shipping company. We're protecting their local Exchange Server and their online Exchange email.

We use it for email filtering, spam filtering, for phishing attacks, malware, and forged-email detection. We also use it for outbound message control, to filter attachments that are allowed to be sent and attachments that are not allowed to be sent. It's for data loss protection.

It's pretty normal daily incoming and outgoing emails. We have customized policies based on our security measures using this tool to scan the emails in our inboxes. We also check all incoming emails.

We are using two security appliances. One is a web security appliance, IronPort, as well as the Cisco Secure Email Gateway. They are used for web surfing.

i'm usining it as frontal gateway for controlling and securing the mails flows to my on-premises exchange servers

It is just another level of protection that we use, as far as email is concerned. We use it for different policies or as another scanning engine, e.g., on the desktop or for data coming through another email gateway.