The Future of Microsoft Security 1'1

1
The Future of Microsoft Security 1.1

• Paul ThurrottNews EditorWindows .NET Magazine

2
About Paul

• Daily WinInfo UPDATE
• Weekly Windows .NET Magazine UPDATE
• Bi-weekly .NET UPDATE, Connected Home Express
  (commentary, news, tip)
• Monthly Windows and .NET Magazine Need to Know
  column
• SuperSite for Windows
• Books.

3
About Paul

• thurrott_at_winnetmag.com
• http//www.wininformant.com
• Slides and updates will be posted to the
  SuperSite for Windows
• http//www.winsupersite.com

4
Who do you trust?

• Show of hands How many people trust Microsoft?

5
Who do you trust?

• One year into Trustworthy Computing, security
  experts still give Microsoft mixed grades.

6
The Problem

• A legacy of making computing (too) easy.
• Products not architected for security.
• Disparity of systems.
• The Big Brother syndrome.

7
Microsofts Plan

• Now Windows 2000 Service Pack 3 (SP3) Windows
  XP Service Pack 1 (SP1).
• April 24, 2003 Windows Server 2003.
• 2003 Server product wave built on Windows Server
  2003.
• 2004-5 Next Generation Secure Computing Base
  (Palladium Initiative).

What happened to .NET?
8
Windows 2000 Service Pack 3Windows XP Service
Pack 1

• Original releases delivered before Trustworthy
  Computing.
• Not engineered primarily for security.
• Proof XPs UPnP vulnerability.
• XP SP1 release delayed to include Trustworthy
  Computing code updates.

9
Windows 2000 Service Pack 3Windows XP Service
Pack 1

• Set ProgramAccess and Defaults - Consent decree
  compliance.
• Post-RTM security fixes and hot-fixes.
• Trustworthy Computing code review updates.

10
Also in Windows XP SP1

• New capabilities Support for USB 2.0, optional
  .NET Framework, enabling technologies for Windows
  XP Media Center Edition XP Tablet PC Edition.
• New SP1a release last week ditches Microsofts
  Java. SP1b is on hold, pending the results of
  Suns lawsuit.

11
Windows XP Service Pack 1

• New wireless security features
• Protected Extensible Authentication Protocol
  (PEAP)
• A new wireless security option aimed at small
  businesses.
• Password authentication without a PKI
  infrastructure.
• Wi-Fi Wired Equivalent Privacy (WEP) enabled by
  default less friendly, more secure.

12
Windows Server 2003Branding is fun!

• Whistler Server
• Windows 2002 Server The fat lady hasnt sung
  yet.
• Windows .NET Server The final branding.
• Windows .NET Server 2003 Seriously, this is
  the name.
• Windows Server 2003 We should have done this
  six months ago.

13
Windows Server 2003

• Windows Server 2003 Web Edition
• Windows Server 2003 Standard Edition
• Windows Server 2003 Enterprise Edition
• Windows Server 2003 Datacenter Edition
• Windows Server 2003 64-Bit Enterprise Edition
• Windows Server 2003 64-Bit Datacenter Edition
• Windows Server 2003 Embedded Edition
• Windows Small Business Server 2003
• ... And probably 3-4 others I cant remember and
  dont have room for on this slide.

14
Windows Server 2003

• Many small improvements
• IIS 6.0
• .NET as an integrated part of platform
• Storage improvements
• Big management, AD improvements
• Massive performance/scalability improvements
• Security features all about reducing the attack
  surface with ICF, improvements to EFS, Kerberos,
  PKI, etc.

15
Windows Server 2003 Security
Windows Server 2003 is secure by design,
secure by default, and secure in deployment. A
finely crafted sound bite
16
Windows Server 2003 Secure by Design

• Trustworthy Computing initiative Basic redesign
  of the Windows Server product. Development halted
  for 2-3 months.
• .NET Common Language Runtime (CLR) integration
  creates a secure in-OS runtime environment.

17
Windows Server 2003Secure by Design

• (More) secure wireless networks
• 802.1x wireless standard with Extensible
  Authentication Protocol (EAP) for dynamic key
  determination Addresses authentication
  limitations in Wired Equivalency Protocol (WEP).
• Protected Extensible Authentication Protocol
  (PEAP) for encrypted password-based
  authentication. Enhances security of wireless
  connections in non-PKI environments.
• IAS (Internet Authentication Service)
  improvements make it easier to deploy and support
  multiple RADIUS servers. Big new feature Support
  guest users through 802.1x authentication.

18
Windows Server 2003Secure by Design

• Core file encryption capabilities
• Offline Files Database cache is now encrypted.
  Big customer request.
• Encrypting File System (EFS) Debuted in Win2K,
  somewhat improved in this release with support
  for shared EFS volumes, the ability to authorize
  additional user access, and EFS in Web Folders.

19
Windows Server 2003Secure by Default

• IIS 6
• Not installed by default, or because of other
  service installations as before.
• Locked down when installed Dangerous services
  disabled when IIS is turned on, and IIS can only
  serve static Web pages.
• Warnings when admin turns on services.
• Thread pooling and multiple Web servers
• More services shut off or run in lower priorities
  by default.

20
Windows Server 2003Secure by Default

• Internet Explorer Enhanced Security Configuration
  (IE Hard)
• Default configuration of IE security is changed
  to High.
• Reduces exposure of server to Web sites that
  might pose a security risk.
• Will prevent many Web sites from displaying
  properly (Its a server not a surfboard.)
• Necessary sites can be added to Trusted Sites
  list.

21
Windows Server 2003Secure in Deployment

• Software Restriction Policies (SRP) -
  Policy-based technology to enforce which
  applications users can and cannot run. Fights
  Trojans and viruses. Requires Windows XP on the
  client.
• New Group Policy Management Console Two modes,
  Modeling (planning) and Results (what happened?).
  GPs are a great way to deliver secure machine
  configurations, but difficult to use in Win2K.
• Smartcards for admins Logon with a normal user
  account but use a smartcard for admin tasks to
  run tools with administrative privileges. Second
  layer of authentication.

22
Built on Windows Server 2003

• Its going to be a busy year
• Trustbridge Federated identity management and
  .NET Passport integration. A security proxy
  server integration point deployed at edge of
  network.
• Unnamed DRM Server in 2003.
• Management server and E-business server
  (Greenwich) product consolidations.
• .NET My Services Server.
• Exchange Server 2003 SQL Server Yukon.

23
Next Generation Secure Computing Base
(Palladium)

• A new security architecture.
• Perhaps the most misunderstood technology since
  Bob (and yes, youre still using Bob today).
• Hardware/software solution.
• Requires an underlying OS like Windows. It will
  be ported to other operating systems - PDAs, cell
  phones, and other devices. Interoperability is
  the key to ubiquity.

24
Next Generation Secure Computing Base
(Palladium)

• Most likely part of Longhorn Windows release.
• Optional OS component with a software run-time
  environment and protected area of hard drive
  called the Vault that is impervious to software
  attacks.
• Requires special AMD or Intel CPUs and chipsets,
  an all-new PC architecture.

25
DRM?

• Palladium is not DRM.
• DRM is not Palladium.
• DRM is traditionally a software-only solution.
  Palladium adds the hardware element, and is an
  excellent platform for DRM to run on.
• Everybody confuses DRM with Palladium. Microsoft
  filed patent for DRM computer and Bill G.
  discussed DRM in Fortune article about Longhorn.
• Publications seek drama over news.

26
Next Generation Secure Computing Base
(Palladium)

• A major pillar of the Trustworthy Computing
  initiative.
• Protects critical software systems and user data
  by controlling transactions between users or
  processes.
• A software notary can prove things between these
  entities in order to ensure integrity of
  transaction.
• Three integrity areas - Machine integrity, data
  integrity and user integrity.

27
Next Generation Secure Computing Base
(Palladium) Summary

• Billion points of light. i.e. no one
  understands it.
• Pie in the sky Unclear how its going to play
  out. Years away from fruition. Still in flux.
• A major investment by Microsoft in security,
  trust, and responsibility.
• Unclear how much of this vision Microsoft will
  deliver. Longhorn has many other critical
  components as well (SQL-based file system, 3D
  user interface, deep Web services integration,
  etc.). Palladium is not a technology that can be
  dribbled in over time. Its all or nothing.

28
Thanks!

• Paul Thurrott
• thurrott_at_winnetmag.com
• Slides and updates available athttp//www.winsupe
  rsite.com