Introduction to Forefront Security For SharePoint

Why Implement ForeFront with your SharePoint environment?
Implementing ForeFront within your SharePoint environment has several purposes. Most evident, and apparent within initial deployment, is to harden your SharePoint environment since it will begin to accumulate several business process within an arbitrary organization. Since several processes will be automated or reinvented with the introduction of SharePoint into your corporate environment, so it is best to implement complimentary software that will help you mitigate these threats to reduce risks to your communications and collaboration platforms.
There are several portions that make up the FSSP framework:
  • Client
  • Service
  • Central Manager
  • Quarantine Manager
  • ForeFront Web Parts
What is the real purpose of ForeFront then?
Although there are several portions that create the ForeFront framework, the clearest purpose of ForeFront is to clean your content repositories or malicious content to prevent system downtime on your server or on your client machines tied into your SharePoint environment. It works similar to several AV engines, using proactive scanning mechanisms to ensure content filtering and document quarantine and progressive cleaning leveraging multiple engines. The most powerful, and useful, scanning features is managed scanning of your SharePoint document libraries, through both realtime protection, and on-demand routines. This scanning extends to sister server platforms, allowing ForeFront to work with your Microsoft exchange environment as well. The WebParts are somewhat negligible, allowing views into current cleaning metrics, but the real power of ForeFront is the management of documents infected with malware within your repositories.