Video Screencast Help

Observation / Question

Created: 29 Jan 2008 • Updated: 21 May 2010 | 2 comments
Two things that have I find strange:
 
1) Does anyone else find it odd that SEP requires mixed mode authentication (with a disclaimor) when Windows Authentcation Mode is more secure.  I can understand the need to support mixed mode, but not the requirement of mixed mode.  I currently have NO instances of SQL running in mixed mode, I would have to either make my current SQL less secure or create a whole new install of SQL.  I can not use the embedded database because I have too many endpoints.
 
2) Does anyone else find it odd that SEP requires File and Printer Sharing be turned on for product updates to be pushed out.  I can understand this need for initial deployment, but once SEP gets its hooks into your machine would one not expect it could update the application (if the admin desired).  It already gets definition updates without File and Printer Sharing turned on.  I have NO instances of F&P on my workstations, why would I need to make them less secure in order to "Protect" them?
 
Just two things I have noticed.  Understand, these are honest questions, they are not meant to be an insult toward Symantec.  I would love to see changes made to the product or maybe I am reading the docs wrong and someone can correct me.  Please share similiar or opposite views.  Any insight is appreciated.

Comments 2 CommentsJump to latest comment

symantec hurt me's picture
It is also odd that SEP totally messes up the registry keys for Routing and Remote Access.  It does not seem to make any sense that an AV application would have to disable the VPN in order to run.
 
SEP messes up systems more than it protects them
Thom Powell's picture
That is one of the best account names I have ever seen.  Thanks for your reply and I understand your sentiment, but I think my point (or question) may have been missed.  What you have described seems to be problems caused from a poorly coded product that has not been tested properly, aka bugs.  What I am describing are documented truths of how this product is required to be configured in order to work "properly". 
 
So my request is that someone explain to me why I would intentionally open up holes on every endpoint I wish to protect and my SQL databases?  Especially when it does not appear to be neccessary.  If I can update my dat files without F&P turned on, why not my application?  If I have 7 other products that use "windows authentication" in SQL, why can't SEP?
 
I just want to understand.  Any help?