SMBF Deployment Models

1. SMBF Deployment Models Standard Deployments, SDK, & BEIK deployments Nov. 4th 2008

2. SMBF: Deployment Models Overview There are 3 deployment models for installing SBMF at a customer site: • Standard Installation • SDK deployment • BEIK integration

3. SMBF: Deployment Models Standard Deployments

4. SMBF: Standard Deployments In a standard or traditional deployment the model is similar to the diagram: MTA SBMF Client SBMF Scanner

5. SMBF: Standard Deployments 1: The email is send to the MTA. MTA 2: The Client that plugs into the MTA, tells the MTA to wait while it processes the e-mail. SBMF Client 3: The SBMF Scanner scans the e-mail and gives a verdict. SBMF Scanner 4: Client passes verdict to MTA 5. Based on MTA rules action is taken

6. SMBF: Standard Deployments MTA • Things to Note: • The client plug-in for the MTA is created for specific MTA that Symantec Engineering has provided a pre-compiled client for. Specifically, this is only done for sendmail, sendmail switch and Microsoft's IIS. • The MTA/Client and the scanner can be on separate servers or on the same server. The key is that we provide the application/installer for the client and the scanner. • Customers can get 3rd party MTA plug-in clients (like for SUN Messaging) that the 3rd parties compile and provide. Symantec is not responsible for these clients and if there are issues with them, the 3rd party needs to be contacted to address them. SBMF Client Scanner

7. SMBF: Deployment Models SDK Deployments

8. SMBF: SDK Deployments In a SDK deployment the model, the customer creates their own MTA integration with the SDK tools and documentation provided by Symantec. MTA SMBF SDK SBMF Scanner

9. SMBF: SDK Deployments MTA • Things to Note: • Like in the standard deployment, the MTA still pauses when delivering e-mails until the Scanner can give a verdict. • The MTA and ‘client’ are not separate applications in this scenario. The typical SDK deployment has the customer loading the SDK API into the MTA, and then performing the ‘plug-in client’ tasks by itself. • This model works by the MTA loading the SDK components into its process (dlls or so resources files). This allows the MTA to make the API calls to the scanner directly. • Customers that want to use the SDK, need to get sign off from the PM (Elliot Tilley). The customer needs to be made aware of the risks, their responsibilities, and the limited support that will be given for their deployment. Basically we support the SDK’s API calls but not how the customer is using them. If there is an error in the code we will help them. If they are calling the functions wrong, they are on their own. • Like with standard deployments the scanner can be on the same server but, typically is on a remote server. • For customers that was to use Sun’s Java Message Server, the PM (Elliot Tilley) and the customer’s TAM need to be contacted. They are required because the Sun JMS integration with the SDK is not a platform that the Support has been trained on.  A customer who is running on that platform can get support for SBMF, but they will not be able to get support for the Sun side of the implementation and configuration. SMBF SDK SBMF Scanner

10. SMBF: Deployment Models BEIK Integrations

11. SMBF: BEIK Deployments • BEIK deployments take the SDK approach to the ultimate level. In this scenario, the customer is only referencing the SBMF libraries. • In this scenario the MTA does it all. There is no client as there is no need to do remote calls to a scanner. The MTA acts as a scanner by being a home-made ‘wrapper’ around the SMBF rules and libraries. MTA Rules Libraries Definitions

12. SMBF: BEIK Deployments To put it another way… The customer rips out all the ‘meat’ of the scanner that does the real scanning of the messages (the rules, updates, etc…) and builds their own application to apply those rules to messages. SBMF Scanner Rules Rules Libraries Definitions Agent Conduit Harvester Stats

13. SMBF: BEIK Deployments To put it another way… The customer rips out all the ‘meat’ of the scanner that does the real scanning of the messages (the rules, updates, etc…) and builds their own application to apply those rules to messages. SBMF Scanner MTA Rules Rules Rules Libraries Libraries Definitions Agent Definitions Conduit Conduit Harvester Stats

14. SMBF: BEIK Deployments Things to Note: • There are only 2 known customers at the moment that use this deployment model: Hotmail & Biznanga • Customers typically use this method for performance gains by not having to traverse network or application layers to scan messages. • There is no Engineering or customer data to support there are speed gains for BEIK deployments. • If a new customer is looking to use the BEIK, chances are they are probably not choosing the right approach. Deploying the BEIK is complex, time consuming, and does not offer any substantial benefits over the standard deployment of SBMF or even deploying with the SDK for SBMF. • If a customer is sure that they want to deploy the BEIK, have them discuss this with the Product Manager for SBMF and the appropriate Regional Product Manager for the customer: SMBF Product Manager : Elliot Tilley elliot_tilley@symantec.com APAC Product Manager: Masanori Nishjima Masanori_nishjima@symantec.com EMEA Product Manager: Ian McShane ian_mcshane@symantec.com NAM Product Manager: Mark Friedlander mark_freidlander@symantec.com MTA Rules Libraries Definitions Conduit

15. End Useful KBs: • INTERNAL: How to obtain the SDK for Symantec Brightmail Message Filter (KB 2007011709083563) • INTERNAL: What is BEIK? (KB 2008103010171154)