MetaDefender Cloud Prevention API: Malware and File Security for AWS

My main use case for MetaDefender is to secure files uploaded through our applications, as I use it to scan files for malware before processing or storing them, which helps automate threat detection, reduce security risks, and ensure only safe files enter our systems.

One specific example of how I've used MetaDefender in a real scenario would be during a document upload workflow, where when a user uploads a PDF or Word file, MetaDefender scans it for malware before the application processes it, blocking a file if a threat is detected, while allowing it to move forward for processing otherwise, thus preventing malicious files from entering our systems, as I automate most of the workflows or processes that involve uploading a document or a PDF or a Word file.

Another useful aspect of MetaDefender in my daily workflows is automation, as it can integrate with my existing workflows through APIs, allowing file scanning to happen without manual intervention, which helps reduce my team's workload while maintaining consistent security checks.

The biggest positive impact of MetaDefender on my organization has been automating file security checks, which reduces manual effort, as there are lakhs of files being uploaded and manually checking each file has its limits, making the file upload process more secure, saving my team time, and allowing us to focus on other development tasks.

Regarding metrics, I haven't tracked exact numbers yet, but I've noticed less manual effort in checking uploaded files, with the automated scanning making the process more efficient and helping me identify suspicious files earlier, thus improving both security and workflow efficiency, although I don't have specific numbers to share.

The best features MetaDefender offers would include multi-scanning, Deep CDR, and API integration, where multi-scanning uses multiple antivirus engines for better threat detection, Deep CDR removes potentially harmful content from files, and API integration is especially useful because it allows me to automate security checks within my existing workflows.

The feature I rely on most is multi-scanning, as I handle file uploads regularly, and scanning with multiple antivirus engines gives me better threat detection rather than relying on a single engine, thus adding an important layer of security before files are processed.

Another helpful feature I would like to add is detailed scan reports, as they give me visibility into detected threats and scan results, making it easier to investigate suspicious files and troubleshoot issues if necessary; this is useful for both my development and security teams.

I believe MetaDefender could improve its dashboard and reporting to make scan results easier to understand, and I would appreciate more detailed error messages and simpler API documentation to help developers troubleshoot issues faster, as I find the API documentation a bit difficult to understand.

One area I would like to see improved is scanning performance, especially when handling large files or multiple uploads at once, as faster processing and clearer API error messages would make integration smoother and help reduce delays in my workflows, especially during surges in PDF uploads when workflows have been halted or paused.

I am relatively new to MetaDefender, but I have been exploring its key features, including multi-scanning, Deep CDR, malware detection, and file security, and I have a good understanding of how it helps organizations protect their systems from file-based threats, having used it for around the past six months.

On a scale of one to ten, I would rate MetaDefender as an eight out of ten, as my experience with it is pretty positive due to its strong security features and good automation capabilities, although there is still room for improvement in performance, reporting, and ease of integration.

I chose eight specifically because MetaDefender does a great job with malware detection, multi-scanning, and automation, meeting my core security needs; however, improvements in scanning speed, reporting, observability, and developer experience are necessary for a higher rating.

Regarding MetaDefender's AI capabilities, I think it has strong security and governance capabilities, as its AI-powered threat detection helps identify suspicious files, and centralized policies control how threats are handled, although I would appreciate more transparency into AI-based decisions.

Overall, I believe MetaDefender provides reliable threat detection, especially with its multi-scanning approach, and it generally meets my expectations, though false positives can occasionally be a concern, so I recommend reviewing suspicious results rather than relying entirely on automated decisions.

I use MetaDefender in a cloud-based setup, integrated with my application through APIs, which allows me to automatically scan uploaded files before processing them without managing the scanning infrastructure.

I am using OPSWAT's cloud-hosted MetaDefender service, meaning I don't directly manage its hosting infrastructure, and my applications connect to it through APIs for file scanning and threat detection.

I have shared everything I know in detail, and I hope this review helps those who read it.

I would recommend starting with a small proof of concept to test detection accuracy, scanning speed, and API integration, as well as evaluating the pricing and how it fits your existing workflows, especially since this makes sense when there is a lot of sensitive data and large amounts of files being uploaded.

My main use case for MetaDefender is scanning and sanitizing files before they enter our internal environment, where we mainly focus on identifying malicious files and preventing potential threats from spreading through the network.

MetaDefender fits into our broader security strategy as a pre-ingest control, preventing malicious content from entering our system before it can trigger alerts elsewhere.

Overall, the process with MetaDefender has been quite effective for my team, giving us an extra layer of security, especially when receiving files from outside sources, resulting in better visibility, reduced risk, and more confidence when allowing legitimate file transfers.

The positive impact of MetaDefender includes improving file security and reducing manual checks, as the multiple scanning engines and CDR help catch suspicious files and strip harmful content.

MetaDefender saves time by reducing how much manual file verification my team needs to do, scanning files in a single workflow instead of checking each file from external sources one by one.

Combining multiscanning with CDR strengthens my data security operations by providing deeper detection and safer file outputs before files enter the environment.

The recent enhancements to policy orchestration and engine parallelization have improved workflow automation by making it faster and more reliable.

In my view, the strongest feature of MetaDefender is the layering, combining multiple antivirus engines with Content Disarm and Reconstruction.

For my daily operations, CDR stands out most because it directly reduces the risk from incoming documents, which is a constant pain point.

I am using the expanded file type and archive coverage feature, which lets me inspect different types of files rather than just common formats, improving my security coverage.

I use enhanced reporting and audit visibility features, which help me keep clear records of file scans, detected threats, and sanitization results for audit purposes.

My impression of the detection rates provided by MetaDefender's multiscanning is quite positive, as using multiple antivirus engines increases the likelihood of catching threats.

I see deep CDR as one of the most valuable features of MetaDefender, effectively removing malicious content while reconstructing clean, usable files.

The solution effectively enforces security policies around file handling by combining multiple antivirus engines and deep CDR to identify and sanitize suspicious files.

I think the file-based vulnerability assessment feature is valuable, as it helps identify potential security risks in files before they are deployed into production.

I understand the purpose of adaptive sandbox analysis and its benefits for analyzing suspicious files, which adds context for investigating unknown threats.

MetaDefender is strong, but integration with SIEM and SOAR platforms could be smoother, and faster scanning for large files would be welcome.

A clearer user interface would make MetaDefender more intuitive, along with more detailed documentation, implementation guides, troubleshooting resources, and quicker technical support.

I subtracted two points mainly because of the user interface and reporting limitations, alongside some performance lag when scanning larger files.

I have been using MetaDefender for around three years, focusing on cybersecurity operations and Linux administration.

I have worked with MetaDefender for a few months, mainly around file sanitization and scanning workflow, integrating it into my security stack, and testing CDR outputs on typically official documents.

MetaDefender has been stable in my environment, maintaining consistent performance post-integration with no major outages.

In my experience, MetaDefender demonstrates good scalability, able to handle increasing file scanning requirements through automation.

The customer support for MetaDefender has been responsive and helpful whenever I had questions or needed assistance.

I previously relied on traditional antivirus tools but switched to MetaDefender because it provides a more comprehensive security approach.

I have seen a positive return on investment with MetaDefender, improving efficiency by reducing manual work and allowing my security team to focus on important tasks.

My experience with pricing, setup cost, and licensing for MetaDefender has been fairly reasonable, offering good value for its security capabilities.

Before choosing MetaDefender, I evaluated several antivirus alternatives and found that it combined multiple scanning engines and Content Disarm and Reconstruction in one solution.

I would rate MetaDefender an 8 out of 10, as it offers strong malware detection, effective file sanitization, and useful integration, but still has room for improvement.

I think MetaDefender's AI capabilities are helpful for spotting suspicious files and detecting threats while emphasizing the importance of data privacy, transparency, and access control.

MetaDefender generally meets my expectations in terms of accuracy and reliability, bolstered by the multiple antivirus scanning engines that enhance confidence in identifying malicious files.

I primarily use an on-premises deployment of MetaDefender for better control over sensitive files and integration with my existing Linux-based infrastructure.

I advise others looking into using MetaDefender to assess their file transfer workflow and carefully plan the integration into their existing infrastructure.

My current use cases for MetaDefender are providing security to web content and file security over our internal application hosted externally where end users are uploading files on our website. I ensure that files are scanned on MetaDefender Core using MetaDefender ICAP.

A quick example of when I used MetaDefender is when we had an internal shared drive folder that was publicly exposed and our clients were using that shared drive. When they uploaded their designing documents or ZIP files, if the file had a malicious hash value, MetaDefender would break that hash value, break that ZIP and find the hash value. According to the antivirus engine's scan verdict, it would block that file.

Apart from that, for web content using HTTP protocol, we monitor the POST method. Whatever request is carrying, such as XML script or JavaScript, is also scanned by MetaDefender. If someone tries to make code changes over the publicly hosted applications, MetaDefender Core will block it by determining that the particular request is not a valid request.

MetaDefender has positively impacted our organization as we have noticed that end-users, clients, or hackers attempting to upload any malicious content towards our URL or application can be detected easily, and we have good exposure and visibility towards those particular threats.

I must say that there are faster responses in scanning the file and providing the verdict of that particular file. Accordingly, it takes action to block or allow that file. If it has been detected as clean reputation, then it will be allowed, and there would be no specific things needed to be done. However, if the hash value is detected by any of the engines as malicious, then it will be blocked immediately.

The integration of multi-scanning and Content Disarm and Reconstruction with MetaDefender has made things much easier and more secure.

The best features that MetaDefender offers are providing multiple scan engines, so if one scan engine fails to scan the file or the hash value is mentioned as clean according to one scan engine, yet that file is malicious, then another engine may detect that as malicious according to their current signature. There are multiple scan engines, around eighteen, so even if one detects the file as malicious, it will be blocked. That feature is very useful.

Additionally, MetaDefender is providing AI content detection, so if a file, image, or something that is created using an AI tool, it will detect that file by breaking that value and hash values.

Apart from that, MetaDefender provides workflow settings where I can control the request and how I want to proceed with the scanning, the timeout settings I can provide, ZIP file settings, and how I want to perform scanning on archive files. I can also see that visualization in the console itself. All these are very good features, and apart from MetaDefender, I haven't seen any product have these features.

Regarding MetaDefender's AI capabilities, it provides AI content detection based on their scan engines and all those verdicts. It provides detection for PNGs, JPEGs, or any file that has been created using an AI tool. This is the only feature I have worked on so far.

The accuracy and reliability of the output from MetaDefender's AI capabilities are consistent, and I don't think they are failing to detect actual AI-generated files.

Since we have much more resources than requested for MetaDefender, I'm not seeing much impact on the archive file scanning.

For audit visibility, there is an option for checking the audit event, so we can extract that report as well. It helps us find out what changes have been made and if our compliance policy and configuration are up to our compliance policy or not. Using audit logs, we can validate those things.

Deep CDR is a strong feature of MetaDefender that we have configured using a sandbox license. While it is scanning the file, it breaks the file and checks each component of that file. By using the sandbox feature, it will isolate the particular file temporarily and check whether anything suspicious is detected. If there is a malicious threat, it will remove that and reconstruct the file, providing the copy to the user. That is a very strong feature provided by MetaDefender.

The effectiveness of the solution in blocking or sanitizing content based on policy has totally met our expectations, as we have already configured the workflow according to our use case. It takes action against the files based on our configured settings.

Currently, MetaDefender doesn't have a feature such as providing the applications that are under scanning on ICAP and MetaDefender Core. I think that feature needs to be included in future versions because it is configured behind the proxy, and MetaDefender team will not have an idea of which application is there because you can't see that in the dashboard. You have to check the processing history, and there you can check which request is coming and which application traffic is coming. So we can't have an overall view for these particular settings. I think they need to work on this feature so users have consolidated data for the applications that are already integrated with MetaDefender Core for scanning purposes.

Apart from this, I think the archive extraction is taking much more time even if we have much more than enough resources. I'm not saying the required specifications needed for particular scan engines need to be met, but we are having much more resources than requested. However, still for archive extraction and scanning, it is taking much more time, causing latency in the current request flow, and most of the files are in queue for two, three, or five seconds, depending on the size of the archive file. Based on their settings, other files have been impacted. They need to work on this as well so that when the archive extraction is happening, it should not impact other requests which MetaDefender is handling currently.

The detection rates provided by MetaScan multi-scanning are effective, but sometimes we see that a file is genuine, and users complain of no harmful hash value that needs to be detected as malicious or a threat. However, even with our license of all eighteen AV scan engines, some genuine files are detected as malicious because of the configuration that says even if one scanning engine detects a file as malicious, that file will be blocked. This sometimes causes issues for us.

I have been using MetaDefender Core and ICAP products for approximately 1.6 to 2 years.

On a scale of one to ten, I would rate MetaDefender an eight.

I gave it an eight because of the two things I already mentioned where they want to work. I can still say nine is perfect, but I will not give ten as I am not satisfied with these two features only. Apart from that, the product is very strong and performing well in the field of file security and web content security.

We do not use adaptive sandbox analysis; we have an on-premises sandbox.

My main use case for MetaDefender is to scan files from chats on a day-to-day basis, because sometimes most of the people are sending something possibly malicious via web chats, and I need to be sure that everything that comes in and comes out of that chat is legitimate and won't affect our company's computer servers.

MetaDefender fits into my workflow for scanning files automatically. We have two MetaDefender Cores working together, and the scanning is working automatically, fast, and smoothly, while we can manually take some files from the quarantine if needed. Everything is automated with the API, so that is how we actually use it.

During my studies, I don't really trust files from the outside, even from my professors or the internet, so I constantly scan them in MetaDefender Core and I appreciate the results. I appreciate how fast it works, and it is easy to manage, implement, and work with.

MetaDefender has impacted my organization positively because we hear from our customers that everything works fine. I don't have a lot of support tickets about things being broken or working poorly and don't need to upgrade the whole system every week, so everything is great.

The outcomes from using MetaDefender Core include scanning metrics reaching a few milliseconds if you know how to configure it right. This year, I received a few tickets about configuration requests, but none regarding something being broken. Everything worked well and smoothly.

The best features MetaDefender offers in my experience include how easily it installs and the great GUI that I find excellent, even though I feel quite confused with the new version. I appreciate how everything connects smoothly, which allows my workflow to cover more directions in my company.

I find the new GUI confusing only because I am used to the previous one. While it is common to need time to adjust to a refreshed GUI, overall, the GUI is still one of the best I have ever seen. Connecting different modules is easy to do, just as installing on your Linux or Windows system and configuring it to work out of the box is straightforward.

I have a great impression of the detection rates provided by MetaScan multi-scanning. It is one of the best I have ever seen.

I assess the effectiveness of Deep CDR in reconstructing files safely and without signatures as a ten out of ten, as I really appreciate how it is done.

The file-based vulnerability assessment feature is useful for identifying potential security risks before deployment, as it helps to detect vulnerabilities at an early stage and reduces the risk of introducing vulnerable components into production environments.

We use the adaptive sandbox analysis, and I appreciate it because it operates on a separate server, MetaDefender IFR. I appreciate the GUI, the design, and the overall reports it generates.

We are using the enhanced reporting and audit visibility features because the reports are very colorful and everything we need is beautifully presented.

I assess the effectiveness of the solution in blocking or sanitizing content based on policy as a ten out of ten.

MetaDefender could be improved by enhancing the Central Management feature because sometimes when I need to make configurations inside MetaDefender Core, it is blocked, which necessitates accessing Central Management. I suggest allowing more settings to be adjustable directly in MetaDefender Core itself.

I have been using MetaDefender Core for a year now, and in addition to Core, I also use other solutions such as Email Gateway Security, MetaDefender IFR, and ICAP.

MetaDefender is one hundred percent stable.

MetaDefender's scalability is straightforward. You can scale by adding multiple MetaDefender Cores that work as a cluster, but you need an external load balancer for this purpose.

We used to use FortiSandbox, but we switched to MetaDefender because it is simply better.

I cannot share any relevant metrics about return on investment as we are not counting that information.

My experience with pricing, setup cost, and licensing has been excellent. When I ask for the price, it takes less than an hour to get all the information I need, and everything is fast.

Before choosing MetaDefender, I cannot really remember evaluating other options besides FortiSandbox and MetaDefender Core, but we ultimately chose MetaDefender Core because it was better.

I have not used MetaDefender's AI capabilities at all because this is a new feature, and both our customers and I have not utilized AI in MetaDefender.

I think the AI capabilities and accuracy of MetaDefender should be at the top based on my expectations, as the product overall is excellent.

My advice for others looking into using MetaDefender is to install it on either a Linux or Windows system, conduct your tests, explore, and you will see that MetaDefender Core is an excellent product.

I rate MetaDefender a ten out of ten.