Hmm, that's a good question. My guess is that the high aggressiveness settings might be configured to focus more on detecting sensitive data or other non-executable file types, and as a result, they might not be as effective at handling executables. But that's just my speculation.
You know, I hadn't even considered the disk space factor. That's a good point. I'm also curious about the statement that high aggressiveness settings don't support executable file types. I wonder what the rationale is behind that.
I agree with you on that. Personally, I'm also worried about the disk space issue. If FortiMail needs more disk space just to handle all the additional rules, that could be a real problem, especially for organizations with limited storage capacity.
This question is a bit tricky, but I think I've got it figured out. The main disadvantages of having a too-high aggressiveness setting are the increased resource usage and the potential for more false positives, which could really slow down the system and cause a lot of headaches.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Alisha
7 months agoYoulanda
7 months agoEdgar
7 months agoThaddeus
7 months agoTracie
7 months agoStephaine
7 months agoQueen
7 months agoJustine
7 months ago