SPTechCon SFO 2012 - Understanding the Five Layers of SharePoint Security
Download as PPTX, PDF1 like987 views
The document discusses the five layers of security in a SharePoint environment: 1) Infrastructure security including physical security, service account setup, and Kerberos authentication. 2) Data security including role-based access control, SQL transparent data encryption, and antivirus. 3) Transport security including SSL and IPSec. 4) Edge security including inbound internet security. 5) Rights management. It then provides details on infrastructure security focusing on best practices for service account configuration and enabling Kerberos authentication between SharePoint and SQL Server.
More Related Content
What's hot (20)
Similar to SPTechCon SFO 2012 - Understanding the Five Layers of SharePoint Security (20)
More from Michael Noel (20)
Recently uploaded (20)
SPTechCon SFO 2012 - Understanding the Five Layers of SharePoint Security
- 1. Understanding the Five Layers of SharePoint Security Michael Noel @MichaelTNoel
- 2. Michael Noel • Author of SAMS Publishing titles “SharePoint 2007 Unleashed,” the upcoming “SharePoint 2010 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles . • Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco, U.S.A. based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
- 3. SharePoint Security Layers of Security in a SharePoint Environment • 1: Infrastructure Security – Physical Security – Best Practice Service Account Setup – Kerberos Authentication • 2: Data Security – Role Based Access Control (RBAC) – Transparent Data Encryption (TDE) of SQL Databases – Antivirus • 3: Transport Security – Secure Sockets Layer (SSL) from Client to Server – IPSec from Server to Server • 4: Edge Security – Inbound Internet Security (Forefront UAG/TMG) • 5: Rights Management
- 4. Infrastructure Security Layer
- 5. Layer 1: Infrastructure Security Sample List of Service Accounts Service Account Name Role of Service Account Special Permissions COMPANYABCSRV-SP-Setup SharePoint Installation Account Local Admin on all SP Servers (for installs) COMPANYABCSRV-SP-SQL SQL Service Account(s) – Should be separate Local Admin on Database Server(s) admin accounts from SP accounts. (Generally, some exceptions apply) COMPANYABCSRV-SP-Farm SharePoint Farm Account(s) – Can also be N/A standard admin accounts. RBAC principles apply ideally. COMPANYABCSRV-SP-Search Search Account N/A COMPANYABCSRV-SP-Content Default Content Access Account Read rights to any external data sources to be crawled COMPANYABCSRV-SP-Prof Default Profiles Access Account Member of Domain Users (to be able to read attributes from users in domain) and ‘Replicate Directory Changes’ rights in AD. COMPANYABCSRV-SP-AP-SPCA Application Pool Identity account for DBCreator and Security Admin on SQL. SharePoint Central Admin. Create and Modify contacts rights in OU used for mail. COMPANYABCSRV-SP-AP-Data Application Pool Identity account for the N/A Content related App Pool (Portal, MySites, etc.) Additional as needed for security.
- 6. Layer 1: Infrastructure Security Enable Kerberos • When creating any Web Applications in Classic-mode, USE KERBEROS. It is much more secure and also faster with heavy loads as the SP server doesn’t have to keep asking for auth requests from AD. • Kerberos auth does require extra steps, which makes people shy away from it, but once configured, it improves security considerably and can improve performance on high-load sites. • Should also be configured on SPCA Site! (Best Practice = Configure SPCA for NLB, SSL, and Kerberos (i.e. https://spca.companyabc.com)
- 7. Layer 1: Infrastructure Security Kerberos Step 1: Create the Service Principal Names • Use the setspn utility to create Service Principle Names in AD, the following syntax for example: – Setspn.exe -A HTTP/mysite.companyabc.com DOMAINNAMEMYSiteAppAccount – Setspn.exe -A HTTP/mysite DOMAINNAMEMYSITEAppAccount – Setspn.exe -A HTTP/home.companyabc.com DOMAINNAMEHOMEAppAccount – Setspn.exe -A HTTP/sp DOMAINNAMEHOMEAppAccount
- 8. Layer 1: Infrastructure Security Kerberos Step 2: Enable Kerberos between SP and SQL • Use setspn to create SPNs for SQL Service Account • SPNs need to match the name that SharePoint uses to connect to SQL (Ideally SQL Alias, more on this later) • Syntax similar to following: – Setspn.exe -A MSSQLSvc/spsql:1433 COMPANYABCSRV-SQL-DB – Setspn.exe –A MSSQLSvc/spsql.companyabc.com:1433 COMPANYABCSRV-SQL-DB • MSSQLSvc = Default instance, if named instance, specify the name instead • In this example, SRV-SQL-DB is the SQL Admin account
- 9. Layer 1: Infrastructure Security Kerberos Step 3: Allow Accounts to Delegate (Optional) • Required only for Excel Services and other impersonation applications. • On all SP Computer accounts and on the Application Identity accounts, check the box in ADUC to allow for delegation. – In ADUC, navigate to the computer or user account, right-click and choose Properties. – Go to the Delegation tab – Choose Trust this user/computer for delegation to any service (Kerberos)
- 10. Layer 1: Infrastructure Security Kerberos Step 4: Enable Kerberos on Web Application • Go to Application Management – Authentication Providers • Choose the appropriate Web Application • Click on the link for ‘Default’ under Zone • Change to Integrated Windows Authentication - Kerberos (Negotiate) • Run iisreset /noforce from the command prompt • If creating Web App from scratch, this step may be unnecessary if you choose Negotiate from the beginning
- 11. DATA SECURITY Layer
- 12. Layer 2: Data Security Role Based Access Control (RBAC) • Role Groups defined within Active Directory (Universal Groups) – i.e. ‘Marketing,’ ‘Sales,’ ‘IT,’ etc. • Role Groups added directly into SharePoint ‘Access Groups’ such as ‘Contributors,’ ‘Authors,’ etc. • Simply by adding a user account into the associated Role Group, they gain access to whatever rights their role requires. User1 Role SharePoint Group Group User2
- 13. Layer 2: Data Security SQL Transparent Data Encryption (TDE) • SQL Server 2008 and 2008 R2 Enterprise Edition Feature • Encrypts SQL Databases Transparently, SharePoint is unaware of the encryption and does not need a key • Encrypts the backups of the database as well
- 14. Layer 2: Data Security TDE vs. Cell Level Encryption • Available with either SQL 2005 or SQL 2008 • Encrypts individual cells in a database • Requires a password to access the cell • Requires that columns be changed from their original data type to varbinary • Advantage is that only specific info is encrypted • Disadvantage is that you cannot use this for SharePoint Databases
- 15. Layer 2: Data Security TDE vs. File Level Encryption • Two forms, older Encrypting File System (EFS) and Bitlocker • EFS encrypts data at the File Level • Bitlocker encrypts data at the Volume Level • Bitlocker Encrypts every file on the disk, not just database files • Could be used together with TDE
- 16. Layer 2: Data Security SQL Transparent Data Encryption (TDE) Limitations • Does not encrypt the Communication Channel (IPSec can be added) • Does not protect data in memory (DBAs could access) • Cannot take advantage of SQL 2008 Backup Compression • TempDB is encrypted for the entire instance, even if only one DB is enabled for TDE, which can have a performance effect for other DBs • Replication or FILESTREAM data is not encrypted when TDE is enabled (i.e. RBS BLOBs not encrypted)
- 17. Key Windows OS Level Hierarchy and Cert Data Protection API (DPAPI) DPAPI Encrypts SMK SQL Instance Level Service Master Key SMK encrypts the DMK for master DB master DB Level Database Master Key DMK creates Cert in master DB master DB Level Certificate Certificate Encrypts DEK in Content DB Content DB Level Database Encryption Key DEK used to encrypt Content DB
- 18. Layer 2: Data Security SQL TDE Step 1: Creating the Database Master Key (DMK) • Symmetric key used to protect private keys and asymmetric keys • Protected itself by Service Master Key (SMK), which is created by SQL Server setup • Use syntax as follows: – USE master; – GO – CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'CrypticTDEpw4CompanyABC'; – GO
- 19. Layer 2: Data Security SQL TDE Step 2: Creating the TDE Certificate • Protected by the DMK • Used to protect the database encryption key • Use syntax as follows: USE master; GO CREATE CERTIFICATE CompanyABCtdeCert WITH SUBJECT = 'CompanyABC TDE Certificate' ; GO
- 20. Layer 2: Data Security SQL TDE Step 3: Backup the Master Key • Without a backup, data can be lost • Backup creates two files, the Cert backup and the Private Key File • Use following syntax: USE master; GO BACKUP CERTIFICATE CompanyABCtdeCert TO FILE = 'c:BackupCompanyABCtdeCERT.cer' WITH PRIVATE KEY ( FILE = 'c:BackupCompanyABCtdeDECert.pvk', ENCRYPTION BY PASSWORD = 'CrypticTDEpw4CompanyABC!' ); GO
- 21. Layer 2: Data Security SQL TDE Step 4: Creating the Database Encryption Key (DEK) • DEK is used to encrypt specific database • One created for each database • Encryption method can be chosen for each DEK • Use following syntax: USE SharePointContentDB; GO CREATE DATABASE ENCRYPTION KEY WITH ALGORITHM = AES_256 ENCRYPTION BY SERVER CERTIFICATE CompanyABCtdeCert GO
- 22. Layer 2: Data Security SQL TDE Step 5: Enable TDE on the Database(s) • Data encryption will begin after running command • Size of DB will determine time it will take, can be lengthy and could cause user blocking • Use following syntax: USE SharePointContentDB GO ALTER DATABASE SharePointContentDB SET ENCRYPTION ON GO
- 23. Layer 2: Data Security SQL TDE Step 6: Monitor the TDE Encryption Progress • State is Returned • State of 2 = Encryption Begun • State of 3 = Encryption Complete • Use following syntax: USE SharePointContentDB GO SELECT * FROM sys.dm_database_encryption_keys WHERE encryption_state = 3; GO
- 24. Layer 2: Data Security SQL TDE: Restoring a TDE Database to Another Server • Step 1: Create new Master Key on Target Server (Does not need to match source master key) • Step 2: Backup Cert and Private Key from Source • Step 3: Restore Cert and Private Key onto Target (No need to export the DEK as it is part of the backup) USE master; GO CREATE CERTIFICATE CompanyABCtdeCert FROM FILE = 'C:RestoreCompanyABCtdeCert.cer' WITH PRIVATE KEY ( FILE = 'C:RestoreCompanyABCtdeCert.pvk' , DECRYPTION BY PASSWORD = 'CrypticTDEpw4CompanyABC!' ) • Step 4: Restore DB
- 25. Layer 2: Data Security SharePoint Antivirus
- 27. Layer 2: Data Security SharePoint Antivirus VSAPI • Realtime scanning only uses the VSAPI • Realtime Scan Settings are Administered through the SharePoint Central Admin Tool – Realtime Options are grayed out in the ForeFront Admin Console
- 28. Layer 2: Data Security SharePoint Antivirus: FPS Keyword and File Filtering • Look for specific keywords (sensitive company info, profanity, etc.) – Block – Simply detect and notify • Create Filter List – Add Keywords, either manually or bulk as lines in a text file
- 29. Layer 2: Data Security SharePoint Antivirus: FPS Profanity Filters • New Profanity lists in 11 languages available in SP2 – (Run KeywordInstaller.msi to install) – Import the lists into FF from Program FilesMicrosoft Forefront SecuritySharePointDataExample Keywords
- 31. TRANSPORT SECURITY Layer
- 32. Layer 3: Transport Security Client to Server: Using Secure Sockets Layer (SSL) Encryption • External or Internal Certs highly recommended • Protects Transport of content • 20% overhead on Web Servers • Can be offloaded via SSL offloaders if needed • Don’t forget for SPCA as well!
- 33. Layer 3: Transport Security Server to Server: Using IPSec to encrypt traffic • By default, traffic between SharePoint Servers (i.e. Web and SQL) is unencrypted • IPSec encrypts all packets sent between servers in a farm • For very high security scenarios when all possible data breaches must be addressed
- 34. EDGE SECURITY Layer
- 35. Layer 4: Edge Security Forefront Unified Access Gateway (UAG) 2010
- 36. Layer 4: Edge Security UAG Comparison with Forefront TMG Capability TMG 2010 UAG 2010 Publish Web applications using HTTPS X X Publish internal mobile applications to roaming mobile devices X X Layer 3 firewall X X* Outbound scenarios support X X* Array support X Globalization and administration console localization X Wizards and predefined settings to publish SharePoint sites and Exchange X X Wizards and predefined settings to publish various applications X Active Directory Federation Services (ADFS) support X Rich authentication (for example, one-time password, forms-based, smart card) X X Application protection (Web application firewall) Basic Full Endpoint health detection X Information leakage prevention X Granular access policy X Unified Portal X
- 37. RIGHTS MANAGEMENT Layer
- 38. Layer 5: Rights Management Active Directory Rights Management Services (AD RMS) • AD RMS is a form of Digital Rights Management (DRM) technology, used in various forms to protect content • Used to restrict activities on files AFTER they have been accessed: – Cut/Paste – Print – Save As… • Directly integrates with SharePoint DocLibs
- 39. Layer 5: Rights Management How AD RMS Works 1. On first use, authors receive client licensor certificate from RMS server 2. Author creates content and assigns rights 3. File is distributed to recipient(s) 4. Recipient opens file, and their RMS client contacts server for user validation and to obtain a license 5. Application opens the file and enforces the restrictions
- 40. Layer 5: Rights Management Installing AD RMS – Key Storage • Select Cluster Key Storage • CSP used for advanced scenarios
- 41. Layer 5: Rights Management Installing AD RMS – Creating the Cluster Name
- 42. Layer 5: Rights Management Installing AD RMS – Using an SSL Cert for Transport Encryption
- 43. Layer 5: Rights Management Allowing SharePoint to use AD RMS • By default, RMS server is configured to only allow the local system account of the RMS server or the Web Application Identity accounts to access the certificate pipeline directly • SharePoint web servers and/or Web Application Service Accounts need to be added to this security list • Add the RMS Service Group, the machine account(s) of the SharePoint Server and the Web App Identity accountswith Read and Excecute permissions to the ServerCertification.asmx file in the %systemroot%inetpubwwwroot_wmcs Certification folder on the RMS server
- 44. Layer 5: Rights Management Client Accessing AD RMS Documents • RMS-enabled client, when accessing document in doclib, will access RMS server to validate credentials
- 45. Layer 5: Rights Management Client Accessing AD RMS Documents • Effective permissions can be viewed from the document • The RMS client will enforce the restrictions
- 46. Session Summary • Determine Security Risk for your SharePoint Environment • Identify any Regulatory Compliance Requirements for SharePoint • Determine which aspects of SharePoint need to be secured, touching on all five layers of SharePoint Security
- 47. Your Feedback is Important Please fill out a session evaluation form drop it off at the conference registration desk. Thank you!
- 48. Michael Noel Twitter: @MichaelTNoel www.cco.com Slides: slideshare.net/michaeltnoel Travel blog: http://sharingtheglobe.com