BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:US/Arizona
BEGIN:STANDARD
DTSTART:19671029T010000
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20160607T034448Z
UID:2E925564-2C62-11E6-B1DA-0050568D2FB3
DTSTART;TZID=US/Arizona:20160608T180000
DTEND;TZID=US/Arizona:20160608T210000
DESCRIPTION:Can we make passwords stronger yet easier to remember than thos
 e typically created to satisfy compliance requirements? Why do some restri
 ctions on password composition\, e.g. a complexity requirement mandating a
  password must contain a letter and a number—actually make passwords wea
 ker and easier to crack. The top three takeaways from this presentation ar
 e:\n\n- Why passwords are not doing the job.\n- How does one describe a co
 mpensating control to an auditor to prove the implemented method is strong
 er than recommended approaches?\n- What other artifacts—e.g. masking\, f
 orced periodic prophylactic password changes—of the recommended approach
  should be revisited?\n\nSpeaker(s): Hoyt L Kesterson II\, \n\nAgenda: \nN
 etworking and light meal from 6-7PM. Speaker at 7PM.\n\nBldg: ITT\, 5005 S
 . Wendler Drive\, Tempe\, Arizona\, United States
LOCATION:Bldg: ITT\, 5005 S. Wendler Drive\, Tempe\, Arizona\, United State
 s
ORGANIZER:askidmore@computer.org
SEQUENCE:0
SUMMARY:Everything We are Doing with Passwords is Wrong
URL;VALUE=URI:https://events.vtools.ieee.org/m/40142
X-ALT-DESC:Description: &lt;br /&gt;&lt;p&gt;Can we make passwords stronger yet easier 
 to remember than those typically created to satisfy compliance requirement
 s? Why do some restrictions on password composition\, e.g. a complexity re
 quirement mandating a password must contain a letter and a number&amp;mdash\;a
 ctually make passwords weaker and easier to crack. The top three takeaways
  from this presentation are:&lt;/p&gt;\n&lt;ul&gt;\n&lt;li&gt;Why passwords are not doing th
 e job.&lt;/li&gt;\n&lt;li&gt;How does one describe a compensating control to an audito
 r to prove the implemented method is stronger than recommended approaches?
 &lt;/li&gt;\n&lt;li&gt;What other artifacts&amp;mdash\;e.g. masking\, forced periodic prop
 hylactic password changes&amp;mdash\;of the recommended approach should be rev
 isited?&lt;/li&gt;\n&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Agenda: &lt;br /&gt;&lt;p&gt;Networking and light meal 
 from 6-7PM. &amp;nbsp\;Speaker at 7PM.&lt;/p&gt;
END:VEVENT
END:VCALENDAR

