E-mail Security School Lesson 3: E-mail Policy Control

News

E-mail Security School Lesson 3: E-mail Policy Control

In lesson three of E-mail Security School, guest instructor Joel Snyder teaches the factors to consider when evaluating and selecting enterprise e-mail security products. You will also learn how to construct requirements definitions for e-mail security and how to evaluate different products to select the best one for your organization.

   Webcast: E-mail security: Taming the beast, part three -- Policy control
   Technical paper: Rules for tools: Buying the right e-mail security product
   Quiz: Have you mastered the essentials of e-mail security?
   About the Instructor
   Lesson 3 Discussion Forum

MAIN MENU
E-mail Security School Home

Lesson 1: E-mail security essentials

Lesson 2: Threats and mitigation strategies

Lesson 3: E-mail policy control

Discussion Forum

  

Webcast: E-mail security, part three: Taming the beast -- Policy control

Guest instructor Joel Snyder discusses architectures for perimeter-based systems to centralize e-mail security efforts. He explains how e-mail security vendors are integrating antispam, antivirus, e-mail security and policy-based controls into single systems. This webcast airs live on Wed., April 27 at Noon ET and is available on-demand thereafter. Participants who register with a valid e-mail address and attend all three course webcasts will receive a certificate of completion from SearchSecurity.com. In addition, through our agreement with (ISC)⊃2;, all CISSPs and SSCPs who attend this webcast can earn 1 CPE credit .

BEGIN THE WEBCAST

Find out how you can earn CPE credits

  

Technical paper: Rules for tools: Buying the right e-mail security product

Learn about the factors to consider when evaluating and selecting enterprise e-mail security products. Guest instructor Joel Snyder will address purchasing criteria, testing procedures and matching product capabilities to business needs.

READ THE TECHNICAL PAPER

  

Final Exam: Have you mastered the essentials of e-mail security?

Take this final exam to assess your knowledge of e-mail policy control, as well as the previous two lessons of E-mail Security School. In order to successfully pass the exam, you need to have studied Lessons 1-3.

TAKE THE FINAL EXAM

  

About the Instructor
@9713
Joel Snyder is a senior partner with Opus One, a consulting firm in Tucson, Ariz. He sent his first network e-mail in 1980, and has been designing and implementing enterprise e-mail systems ever since. He is partially to blame for the X.400 messaging standards and has been trying to atone for them ever since.





  
Security School Discussion Forum

Round out your Security School experience by interacting with our guest instructor Joel Snyder and your peers. The Security School Discussion Forum is an online community where you can find answers, share strategies and give advice.

Check out some of the latest postings:

The pros and cons of dropping attachments
Why isn't dropping certain attachments (pif, scr, etc.) a good practice? I think it's safe to say that most companies have no use for these files. I agree that dropping them is not the ONLY solution, but for many file types, it is a good practice. >>1 new reply

The value of using multiple AV engines
What is the value of using multiple antivirus engines on the SMTP or Exchange front ends? Is this a recommended practice rather than relying on a product with a single engine at the edge? >>1 new reply

Encrypting Outlook/Exchange e-mail
Does standard Outlook/Exchange e-mail going out over the Internet get encrypted, or do we need to do something to make that happen? Is the default S/MIME a type of encryption? >>1 new reply


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy