Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

KoprowskiT_SQLRelayBirmingham_SQLSecurityInTheClouds

•
•
Tobias Koprowski
Tobias Koprowski

This document discusses SQL Server security enhancements in SQL Server 2014. It covers three main topics: 1) Transparent Data Encryption allows encrypting database and log files for protection both during operations and when backing up to disk or Azure. Encryption can use passwords, asymmetric keys, or certificates. 2) Encryption Key Management allows managing encryption keys through PowerShell, SMO, SSMS and T-SQL. Asymmetric keys or certificates used for encryption must be properly backed up. 3) A new "CONNECT ANY DATABASE" permission allows logins to connect to all current and future databases without other permissions in those databases. This facilitates auditing processes.

1 of 61
Download to read offline
Learn, Grow, Adapt 07/10/15 sqlrelay.co.uk/ Nottingham 08/10/15 sqlrelay.co.uk/ Reading 12/10/15 sqlrelay.co.uk/ London 13/10/15 sqlrelay.co.uk/ Bristol 14/10/15 sqlrelay.co.uk/ Cardiff 15/10/15 sqlrelay.co.uk/ Birmingham
Awesome SQL Server conferences on your door step! w: sqlrelay.co.uk t: @sqlrelay_uk SQL Security in the Clouds Independent Consultant @ ShadowLand Consulting http://koprowskit.eu/geek || http://itblogs.pl/notbeautifulanymore
about me • independent consultant, security & licensing auditor • Owner of ShadowLand Consulting • Microsoft Certified Trainer • SQL Server MVP (six… years in a row) • MVP Mentor Program Member • SharePoint Subject Matter Expert at CQURE • active blogger, influencer, technical writer • last 9 years living in Data Processing Center Jungle • last 15 years working arroung banking and ICT • Polish Information Technology Society Board Member • Information Security Systems Association Board Member
1 | Security in a Nutshell 2 | SQL Server Security Best Practices 3 | SQL Server 2014 Security Enhacement 4 | SQL Server Security in The Cloud Summary Appendix AGENDA
KoprowskiT_SQLRelayBirmingham_SQLSecurityInTheClouds
KoprowskiT_SQLRelayBirmingham_SQLSecurityInTheClouds
1 | Security In A Nutshell
Security? What is this? • Security is the degree of resistance to, or protection from, harm. It applies to any vulnerable and valuable asset, such as a person, dwelling, community, nation, or organization. • As noted by the Institute for Security and Open Methodologies (ISECOM) in the OSSTMM 3 (Open Source Security Testing Methodology Manual), security provides "a form of protection where a separation is created between the assets and the threat." These separations are generically called "controls," and sometimes include changes to the asset or the threat.
Categorizing Security - part 1 {IT REALM} • Application security | http://bit.ly/18u8J6p • Computing security | http://bit.ly/1ARdRLd • Data security | http://bit.ly/185wfph • Information security | http://bit.ly/1ARe0ya • Network security | http://bit.ly/1C443R8
Categorizing Security - part 2 {PHYSICAL REALM} • Airport security | http://bit.ly/1LPZcCZ • Food security | http://bit.ly/1MYnii6 • Home security | http://bit.ly/1Gz3VI1 • Infrastructure security | http://bit.ly/1Bm8LIF • Physical security | http://bit.ly/1Gz3VI1 • Port security | http://bit.ly/1ARewMH • Supply chain security | http://bit.ly/1Ex7ob7 • School security | http://bit.ly/17Dl735 • Shopping center security | http://bit.ly/1EUb1FV
Categorizing Security - part 3 {POLITICAL REALM} • Homeland security | http://bit.ly/1AAwZhE • Human security | http://bit.ly/1DhojtU • International security | http://bit.ly/1MYoyli • National security | http://bit.ly/1FEnldu • Public security | http://bit.ly/1wqpX9P
Categorizing Security - part 4 {SQL SERVER REALM} • Application security • Computing security • Data security • Information security • Network security • Home security • Infrastructure security • Physical security • National security • Public security
2 | SQL Server Security Best Practices
SQL Server Security Best Practices • Efficiency and security have an inverse relationship to one another. • You can have high efficiency or high security, but not both. Example: `Small Bank Company` tend to favor efficiency over security: • Cost limitations. This is the first and obvious reason. Community banks are fighting a constant battle to remain competitive. Implementing security in systems adds costs - there is no way around it. • Risk. It's not always a conscious decision for a bank to improve efficiency by sacrificing security. Sometimes there's a lack of understanding of the risks associated with the systems we deploy. • Personnel limitations. The many-hats syndrome runs rampant in smaller community banks. • Regulatory emphasis. The current regulatory environment stresses controls as they relate to policy and procedures.
authentication • SQL Server supports: • Windows Authentication Mode which supports • Kerberos • NTLM (Windows NT Lan Manager) • Mixed Mode Authentication which supports • Windows Accounts • SQL Server specific accounts SECURITY BEST PRACTICES Best Practice: use Windows Authentication mode unless legacy application require Mixed Authentication for backward compability
secure sysadmin account • sysadmin account (sa) is most vulnerable account when it’s not changed • potential SQL Server attackers, hackers aware of this SECURITY BEST PRACTICES Best Practice: change name of sysadmin account after installation SSMS>Object Explorer>Logins>Rename (right click) / T-SQL
use complex password SECURITY BEST PRACTICES Best Practice: ensure that complex password are used for sa and other sql-server-specific logins. Think about ENFORCE EXPIRATION & MUST_CHANGE for any new SQL login
use specific logins Best Practice: use different accounts for different sql-server oriented services Component Windows Server 2008 Windows 7 and Windows Server 2008 R2 and higher Recommended accounts Database Engine NETWORK SERVICE Virtual Account * SQL_Engine SQL Server Agent NETWORK SERVICE Virtual Account * SQL_Agent SSAS NETWORK SERVICE Virtual Account * SQL_srvAS SSIS NETWORK SERVICE Virtual Account * SQL_srvIS SSRS NETWORK SERVICE Virtual Account * SQL_srvRS SQL Server Distributed Replay Controller NETWORK SERVICE Virtual Account * SQL_DRContro SQL Server Distributed Replay Client NETWORK SERVICE Virtual Account * SQL_DRReplay FD Launcher (Full-text Search) LOCAL SERVICE Virtual Account SQL Server Browser LOCAL SERVICE LOCAL SERVICE SQL Server VSS Writer LOCAL SYSTEM LOCAL SYSTEM SECURITY BEST PRACTICES
sysadmin membership • Member of sysadmin fixed-server role can do whatever they want on SQL Server • by default sysadmin fixed-server role has CONTROL SERVER permission granted explicity • do not explicitly grant CONTROL SERVER for Windows logins, Windows Group logins and SQL logins SECURITY BEST PRACTICES Best Practice: carefully choose the membership of sysadmin fixed-server
general administration • everything (almost always) works under sa account especially with CONTROL SERVER permission • institute dedicated Windows logins for DBAs, and assign these logins sysadmin rights on SQL Server for administration purposes. SECURITY BEST PRACTICES Best Practice: use built-in fixed server roles and database roles or create your custom roles, then apply for specific logins
revoke guest access • by default guest accounts exist in every user and system databases • is a potential security risk in lock down environment • those accounts could be targets for attackers • asssign public server role membership if you will need explicit access to user databases SECURITY BEST PRACTICES Best Practice: disable all gueast user access from all user and system databases (excluding msdb database)
limit public permission • SQL Server has many Stored Procedures and many od them have public access permission: • OLE AUTOMATION: sp_OACreate, sp_OAGetProperty, sp_OAStop, sp_OAMethod, sp_OAGerErrorInfo, sp_OADestroy, sp_OASetProperty • REGISTRY ACCESS: xp_regremovemultistring, xp_regaddmultistring, xp_regread, xp_regdeletekey, xp_regdeletevalue, xp_regwrite • OTHER ROUTINES: sp_sdidebug, xp_logevent, sp_sprintf, xp_dsninfo, xp_msver, sp_sscanf, xp_stopmail, xp_grantlogin, xp_eventlog, xp_dirtree SECURITY BEST PRACTICES Best Practice: revoke public role access for some axtended procedures and check other store procedures
hardening sql server ports • default sql server port 1433/1434 is well known as standard target for hackers • by using SQL Server Configuration Manager you: • can change default port • can use specific TCP port intead of dynamic • remeber about similar TCP/UDP ports (1433, 1434) SECURITY BEST PRACTICES Best Practice: change default SQL Server port if it’s possible
disable sql server browser • by default SQL Server Browser is disabled • tt’s necessary to run when multiple instances are running on a single server • any Windows user having the following rights would be capable to run the SQL Server Browser service: • deny access to this computer from the network / deny logon locally / deny logon as a batch job • Deny logon through Terminal Services / log on as a service / read and write the SQL Server registry keys related to network communication (ports and pipes) SECURITY BEST PRACTICES Best Practice: change default SQL Server port if it’s possible
secure service accounts • different service accounts for different services • dedicated low-privileges domain accounts • check membership on a regular basis • use strong and different passwords for each account SECURITY BEST PRACTICES Best Practice: create good plan and make note about service accounts and passwords
3 | SQL Server 2014 Security Enhacements
transparent data encryption • first introduced with SQL Server 2008 • protecting data by performing I/O encryption and decryption for database and log files • passphrase (less secure), asymmetric key (strong protection, poor performance), symmetric key (good performance, strong enough protection), certificate (strong protection, good performance) • New functionality for backup: • takes non-encrypted backup data • encrypt data before writing to disk • compression is performed on the backup data first • then encryption is applied to compressed data • support for backup to Azure SQL14 SECURITY ENHACEMENTS
encryption key management • Encryption options include: • encryption algorithm • certificate or asymmetric key • only asymmetric key reside in EKM is supported • multiple algorithm up to AES-256 are supported • manageable by PowerShell, SMO, SSMS, T-SQL • VERY IMPORTANT: • asymmetric key or certificate MUST be backed up • location MUST be different than backup location • No RESTORE without asymmetric key or certificate SQL14 SECURITY ENHACEMENTS
connect any database • new server-level permission • grant CONNECT ANY DATABASE to a login that must connect to all databases currently exist and any new in future • does not grant any parmission in any database beyond connect • to allow an auditing process to view all data or all database states CONNECT ANY DATABASE may be combined with: • SELECT ALL USER SECURABLES • VIEW SERVER STATE SQL14 SECURITY ENHACEMENTS
impersonate any login • new server-level permission • when granted IMPERSONATE ANY LOGIN allows a middle-tier process to impersonate the account of clients connecting to it • when denied IMPERSONATE ANY LOGIN a high privileged login can be blocked from impersonating other logins • example: CONTROL SERVER permission can be blocked from impersonating other logins SQL14 SECURITY ENHACEMENTS
select all user securables • new server-level permission • when granted SELECT ALL USER SECURABLES a login (for example for auditing purposes) can view data in all databases that the user can connect to SQL14 SECURITY ENHACEMENTS
SQL Server Express Security • by default: • instance name: SQLExpress • networking protocol: disabled • sql server browser: disabled • user (local) instances: • separated instance generated from parent instance • sysadmin privileges on SQL Express on local machine • runs as user process not as service process • only windows logins are supported • RANU instance (run as normal user)
4 | SQL Server Security In The Cloud
Cloud Security Microsoft Cloud Security Approach in a Nutshell • Principles, patterns, and practices • Security engineering • Threats and countermeasures • Secure the network, host, and application • Application scenarios and solutions • Security frame • People, process, and technology • Application, infrastructure, and business http://bit.ly/1zmeYi2
Security Model • uses regular sql security model • authenticate logins, map to users and roles • authorize users and roles to sql objects • support for standard sql auth logins • username + password • {admin, administrator, guest, root, sa} Security model is 100% compatible with on-premise SQL
Security Requirements for Azure Platform Microsoft Azure Datacenters • North America • North-central US - Chicago, IL • South-central US - San Antonio, TX • West US - California • East US - Virginia • Asia • East Asia - Hong Kong, China • South East Asia – Singapore • South America • Brasil – Sao Paulo • Europe • North Europe - Dublin, Ireland • West Europe - Amsterdam, Netherlands • Japan • Japan East, the Tokyo area • Japan West, the Kansai area • Oceania (announced, coming soon) • Sydney, New South Wales • Melbourne, Victoria
Security Requirements for Azure Platform • As a Service Provider Microsoft has an obligation to passing the several rules for security: • ISO 27001/27002 Audit and Certification • SOC 1/SSAE 16/ISAE 3402 and SOC 2 Attestations • Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) • Payment Card Industry (PCI) Data Security Standards (DSS) Level 1
Security Requirements for Azure Platform Also they passing (…) several data securing audits: • Australian Government Information Security Registered Assessors Program (IRAP) • United Kingdom G-Cloud Australian Government IRAP • Multi-Tier Cloud Security Standard for Singapore (MTCS SS 584:2013) • HIPAA Business Associate Agreement (BAA) • EU Model Clauses • Food and Drug Administration 21 CFR Part 11 • Family Educational Rights and Privacy Act (FERPA) • Federal Information Processing Standard (FIPS) 140-2 • Trusted Cloud Service Certification developed by China Cloud Computing Promotion and Policy Forum (CCCPPF) • Multi-Level Protection Scheme (MLPS)
Security Requirements for Azure Platform ISO/IEC 27001:2005 Audit and Certification ISO Scope: The following Azure features are in scope for the current ISO audit: Cloud Services (including Fabric and RDFE), Storage (Tables, Blobs, Queues), Virtual Machines (including with SQL Server), Virtual Network, Traffic Manager, Web Sites, BizTalk Services, Media Services, Mobile Services, Service Bus, Workflow, Multi-Factor Authentication, Active Directory, Right Management Service, SQL Database, and HDInsight. This includes the Information Security Management System (ISMS) for Azure, encompassing infrastructure, development, operations, and support for these features. Also included are Power BI for Office 365 and Power Query Service. SOC 1 and SOC 2 SSAE 16/ISAE 3402 Attestations Scope: The following Azure features are in scope for the current SOC 1 Type 2 and SOC 2 Type 2 attestations: Cloud Services (includes stateless Web, and Worker roles), Storage (Tables, Blobs, Queues), Virtual Machines (includes persistent virtual machines for use with supported operating systems) and Virtual Network (includes Traffic Manager).
Security Requirements for Azure Platform And of course requirements for Data Centers: • Physical security of the data centers (locks, cameras, biometric devices, card readers, alarms) • Firewalls, application gateways and IDS to protect the network • Access Control Lists (ACLs) applied to virtual local area networks (VLANs) and applications • Authentication and authorization of persons or processes that request access to data • Hardening of the servers and operating system instances • Redundant internal and external DNS infrastructure with restricted write access • Securing of virtual machine objects • Securing of static and dynamic storage containers
SQL Server 2005 {9.0} NON-Compability • Common Language Runtime (CLR) and CLR User-Defined Types • Database Mirroring • Service Broker • Table Partitioning • Typed XML and XML indexing is not supported. The XML data type is supported by SQL Azure.
SQL Server 2008 {10.0} NON-Compability • Change Data Capture • Data Auditing • Data Compression • Extended Events • External Key Management / Extensible Key Management • FILESTREAM Data • Integrated Full-Text Search • Large User-Defined Aggregates (UDAs) • Large User-Defined Types (UDTs) • Performance Data Collection (Data Collector) • Policy-Based Management • Resource Governor • SQL Server Replication • Transparent Data Encryption
SQL Server 2008 R2 {10.50} NON-Compability • SQL Server Utility • SQL Server PowerShell Provider • Master Data Services SQL Server Management Studio does not support Windows Azure SQL Database in versions prior to SQL Server 2008 R2
Summary
SQL Server Security in the Cloud • Same security principals like SQL Server on premise • Full responsibility for DBA with Virtual Machine • Partial responsibility for DBA with Azure SQL Database • Automatic updates for Azure SQL Database • New functionality implemented by Microsoft • Some incompabilities with t-sql, functions, store procedures • Increased security by default on Azure platform
SQL Server in Cloud: WASD vs VM Choose Azure SQL Database, if: • You are building brand new, cloud-based applications; or you want to migrate your existing SQL Server database to Azure and your database is not using one of the unsupported functionalities in Azure SQL Database. For more information, see Azure SQL Database Transact-SQL Reference. This approach provides the benefits of a fully managed cloud service and ensures the fast time-to-market. • You want to have Microsoft perform common management operations on your databases and require stronger availability SLAs for databases. This approach can minimize the administration costs and at the same time provides a guaranteed availability for the database. Choose SQL Server in Azure VM, if: • You have existing on-premises applications and wish to stop maintaining your own hardware or you consider hybrid solutions. This approach lets you get access to high database capacity faster and also connects your on-premises applications to the cloud via a secure tunnel. • You have existing IT resources, need full administrative rights over SQL Server, and require the full compatibility with on-premises SQL Server (for example, some features do not exist in Azure SQL Database). This approach lets you minimize costs for development or modifications of existing applications with the flexibility to run most applications. In addition, it provides full control on the VM, operating system, and database configuration.
Three Pillars of a Secure Hybrid Cloud Environment • Pillar One: risk assessment and management • A definition of the risks that apply to various asset(s), based on their business criticality. • An assessment of the current status of each risk before it’s moved to the cloud. Using this information, each risk can be accepted, mitigated, transferred or avoided. • An assessment of the risk profile of each asset, assuming it has been moved to the cloud. • Pillar Two: policy and compliance • Cloud providers need to understand that simply listing compliance certifications isn’t sufficient. In line with the mantra of transparency explored in the previous point, providers should take a proactive stance to sharing their security implementations and controls. Dimension Data often assists clients by providing them with a list of questions that we believe they should be posing to cloud providers as part of the evaluation process, to ensure they’re covering all the bases.’
Three Pillars of a Secure Hybrid Cloud Environment • Pillar Three: provider transparency • Governance: the ability of an organisation to govern and measure enterprise risk introduced by cloud. • Legal issues: regulations, and requirements to protect the privacy of data, and the security of information and computer systems. • Compliance and audit: maintaining and proving compliance when using the cloud. • Information management and data security: managing cloud data, and responsibility for data confidentiality, integrity and availability. • Portability and interoperability: the ability to move data or services from one provider to another, or bring them back in-house. • Business continuity and disaster recovery: operational processes and procedures for business continuity and disaster recovery.
Three Pillars of a Secure Hybrid Cloud Environment • Pillar Three: provider transparency • Data centre: evaluating any elements of a provider’s data centre architecture and operations that could be detrimental to ongoing services. • Incident response, notification and remediation: adequate incydent detection, response, notification, and remediation. • Application security: securing application software running on or developed in the cloud. • Encryption and key management: identifying proper encryption usage and scalable key management. • Identity and access management: assessing an organisation’s readiness to conduct cloud- based identity, entitlement, and access management. • Virtualisation: risks associated with multi-tenancy, virtual machine isolation and co- residence, hypervisor vulnerabilities, etc.
Recommendations • Create a new role for an Information Manager who owns information governance across (all SharePoint) environments • Train and educate all stakeholders about risk and liability • Assess the appropriateness of using SharePoint versus other document management tools • Define information governance policies for access, retention, archival, and backup • Automate risk controls • Audit user and data activities • Resources: • Microsoft TechNet • Microsoft MSDN • Legal Sources for Compliance Requirements
Appendix (Links And Credits)
links • ISECOM (the Institute for Security and Open Methodologies) • http://www.isecom.org/about-us.html • OSSTMM (Open Source Security Testing Methodology Manual) • http://www.isecom.org/research/osstmm.html • Library of Resources for Industrial Control System Cyber Security • https://scadahacker.com/library/index.html • patterns & practices: Cloud Security Approach in a Nutshell • https://technet.microsoft.com/en-us/ff742848.aspx • Microsoft Azure Trust Center: Security • http://azure.microsoft.com/en-us/support/trust-center/security/ • 10 Things to know about Azure Security • https://technet.microsoft.com/en-us/cloud/gg663906.aspx • Security Best Practice and Label Security Whitepapers • http://blogs.msdn.com/b/sqlsecurity/archive/2012/03/07/security-best-practice-and-label-security-whitepapers.aspx
links • Hello Secure World • http://www.microsoft.com/click/hellosecureworld/default.mspx • SQL Server Label Security Toolkit • http://sqlserverlst.codeplex.com/ SQL Server Best Practices Analyzer • Microsoft Baseline Configuration Analyzer 2.0 • http://www.microsoft.com/en-us/download/details.aspx?id=16475 • SQL Server 2005 Best Practices Analyzer (August 2008) • http://www.microsoft.com/en-us/download/details.aspx?id=23864 • Microsoft® SQL Server® 2008 R2 Best Practices Analyzer • http://www.microsoft.com/en-us/download/details.aspx?id=15289 • Microsoft® SQL Server® 2012 Best Practices Analyzer • http://www.microsoft.com/en-us/download/details.aspx?id=29302
links • Microsoft Security Assessment Tool • http://www.microsoft.com/downloads/details.aspx?FamilyID=6D79DF9C-C6D1-4E8F-8000- 0BE72B430212&displaylang=en • Microsoft Application Verifier • http://www.microsoft.com/downloads/details.aspx?FamilyID=bd02c19c-1250-433c-8c1b- 2619bd93b3a2&DisplayLang=en • Microsoft Threat Analysis & Modelling Tool • http://www.microsoft.com/downloads/details.aspx?FamilyID=59888078-9daf-4e96-b7d1- 944703479451&DisplayLang=en • How To: Protect From SQL Injection in ASP.NET • http://msdn2.microsoft.com/en-us/library/ms998271.aspx • Securing Your Database Server • http://msdn.microsoft.com/en-us/library/aa302434.aspx • Threats and Countermeasures • http://www.microsoft.com/technet/security/guidance/serversecurity/tcg/tcgch00.mspx
links • Configure Windows Service Accounts and Permissions • https://msdn.microsoft.com/en-us/library/ms143504.aspx#Network_Service • Select an Account for the SQL Server Agent Service • https://msdn.microsoft.com/en-us/library/ms191543.aspx • Server Configuration - Service Accounts • https://msdn.microsoft.com/en-us/library/cc281953.aspx
azure resources: security • Azure Security: Technical Insights • Security Best Practices for Developing Azure Solutions • Protecting Data in Azure • Azure Network Security • Microsoft Antimalware for Azure Cloud Services and Virtual Machines • Microsoft Enterprise Cloud Red Teaming • Microsoft Azure Security and Audit Log Management • Security Management in Microsoft Azure • Crypto Services and Data Security in Azure
azure resources: security & privacy • Business Continuity for Azure • Understanding Security Account Management in Azure • Azure Data Security: Cleansing and Leakage • Scenarios and Solutions Using Azure Active Directory Access Control • Securing and Authenticating a Service Bus Connection • Azure Privacy Overview (PDF) • Azure Privacy Statement • Law Enforcement Request Report • Protecting Data and Privacy in the Cloud
azure resources: compliance & more • Response to Cloud Security Alliance Cloud Controls Matrix (DOC) • Azure HIPAA Implementation Guidance (PDF) • Azure Customer PCI Guide (PDF) • The Microsoft Approach to Cloud Transparency (PDF) • Microsoft Trustworthy Computing • Operational Security for Online Services Overview (PDF) • Data Classification for Cloud Readiness • CISO Perspectives on Data Classification (PDF) • An Introduction to Designing Reliable Cloud Services (PDF) • Deploying Highly Available and Secure Cloud Solutions (PDF)
azure resources RESOURCE DESCRIPTION MSDN: Azure SQL Database MSDN: SQL Server in Azure Virtual Machines Azure.com: Azure SQL Database Links to the library documentation. Azure SQL Database and SQL Server -- Performance and Scalability Compared and Contrasted This article explains performance differences and troubleshooting techniques when using Azure SQL Database and SQL Server running on- premises or in a VM. Application Patterns and Development Strategies for SQL Server in Azure Virtual Machines This article discusses the most common application patterns that apply to SQL Server in Azure VMs and also hybrid scenarios including Azure SQL Database. Microsoft Enterprise Library Transient Fault Handling Application Block This library lets developers make their applications running on Azure SQL Database more resilient by adding robust transient fault handling logic. Transient faults are errors that occur because of some temporary condition such as network connectivity issues or service unavailability. Since Azure SQL Database is a multitenant service, it is important to handle such errors to minimize any application downtime.
credits • Yes, 123456 is the most common password, but here’s why that’s misleading http://arstechnica.com/security/2015/01/yes-123456-is-the-most-common-password-but-heres-why-thats-misleading/ • CIO’s are Listening, Security is Important… https://communities.intel.com/community/itpeernetwork/blog/2014/05/20/cio-s-are-listening-security-is-important
after session CONTACT: • MAIL: KoprowskiT@windowslive.com • SOCIAL MEDIA: facebook, twitter, linkedin, xing SLIDES FROM SESSION: • SlideShare Profile: http://www.slideshare.net/Anorak • SQL Relay Site: http://www.sqlrelay.co.uk BLOGS: • ITPRO Anorak’s Vision: http://itblogs.pl/notbeautifulanymore/ [PL/EN] • Volume Licensing Specialites: http://koprowskit.eu/licensing/ [PL] • My MVP Blog: http://koprowskit.eu/geek/ [EN/ES/RU/NL/PL]

More Related Content

KoprowskiT_SQLRelayBirmingham_SQLSecurityInTheClouds

  • 1. Learn, Grow, Adapt 07/10/15 sqlrelay.co.uk/ Nottingham 08/10/15 sqlrelay.co.uk/ Reading 12/10/15 sqlrelay.co.uk/ London 13/10/15 sqlrelay.co.uk/ Bristol 14/10/15 sqlrelay.co.uk/ Cardiff 15/10/15 sqlrelay.co.uk/ Birmingham
  • 2. Awesome SQL Server conferences on your door step! w: sqlrelay.co.uk t: @sqlrelay_uk SQL Security in the Clouds Independent Consultant @ ShadowLand Consulting http://koprowskit.eu/geek || http://itblogs.pl/notbeautifulanymore
  • 3. about me • independent consultant, security & licensing auditor • Owner of ShadowLand Consulting • Microsoft Certified Trainer • SQL Server MVP (six… years in a row) • MVP Mentor Program Member • SharePoint Subject Matter Expert at CQURE • active blogger, influencer, technical writer • last 9 years living in Data Processing Center Jungle • last 15 years working arroung banking and ICT • Polish Information Technology Society Board Member • Information Security Systems Association Board Member
  • 4. 1 | Security in a Nutshell 2 | SQL Server Security Best Practices 3 | SQL Server 2014 Security Enhacement 4 | SQL Server Security in The Cloud Summary Appendix AGENDA
  • 7. 1 | Security In A Nutshell
  • 8. Security? What is this? • Security is the degree of resistance to, or protection from, harm. It applies to any vulnerable and valuable asset, such as a person, dwelling, community, nation, or organization. • As noted by the Institute for Security and Open Methodologies (ISECOM) in the OSSTMM 3 (Open Source Security Testing Methodology Manual), security provides "a form of protection where a separation is created between the assets and the threat." These separations are generically called "controls," and sometimes include changes to the asset or the threat.
  • 9. Categorizing Security - part 1 {IT REALM} • Application security | http://bit.ly/18u8J6p • Computing security | http://bit.ly/1ARdRLd • Data security | http://bit.ly/185wfph • Information security | http://bit.ly/1ARe0ya • Network security | http://bit.ly/1C443R8
  • 10. Categorizing Security - part 2 {PHYSICAL REALM} • Airport security | http://bit.ly/1LPZcCZ • Food security | http://bit.ly/1MYnii6 • Home security | http://bit.ly/1Gz3VI1 • Infrastructure security | http://bit.ly/1Bm8LIF • Physical security | http://bit.ly/1Gz3VI1 • Port security | http://bit.ly/1ARewMH • Supply chain security | http://bit.ly/1Ex7ob7 • School security | http://bit.ly/17Dl735 • Shopping center security | http://bit.ly/1EUb1FV
  • 11. Categorizing Security - part 3 {POLITICAL REALM} • Homeland security | http://bit.ly/1AAwZhE • Human security | http://bit.ly/1DhojtU • International security | http://bit.ly/1MYoyli • National security | http://bit.ly/1FEnldu • Public security | http://bit.ly/1wqpX9P
  • 12. Categorizing Security - part 4 {SQL SERVER REALM} • Application security • Computing security • Data security • Information security • Network security • Home security • Infrastructure security • Physical security • National security • Public security
  • 13. 2 | SQL Server Security Best Practices
  • 14. SQL Server Security Best Practices • Efficiency and security have an inverse relationship to one another. • You can have high efficiency or high security, but not both. Example: `Small Bank Company` tend to favor efficiency over security: • Cost limitations. This is the first and obvious reason. Community banks are fighting a constant battle to remain competitive. Implementing security in systems adds costs - there is no way around it. • Risk. It's not always a conscious decision for a bank to improve efficiency by sacrificing security. Sometimes there's a lack of understanding of the risks associated with the systems we deploy. • Personnel limitations. The many-hats syndrome runs rampant in smaller community banks. • Regulatory emphasis. The current regulatory environment stresses controls as they relate to policy and procedures.
  • 15. authentication • SQL Server supports: • Windows Authentication Mode which supports • Kerberos • NTLM (Windows NT Lan Manager) • Mixed Mode Authentication which supports • Windows Accounts • SQL Server specific accounts SECURITY BEST PRACTICES Best Practice: use Windows Authentication mode unless legacy application require Mixed Authentication for backward compability
  • 16. secure sysadmin account • sysadmin account (sa) is most vulnerable account when it’s not changed • potential SQL Server attackers, hackers aware of this SECURITY BEST PRACTICES Best Practice: change name of sysadmin account after installation SSMS>Object Explorer>Logins>Rename (right click) / T-SQL
  • 17. use complex password SECURITY BEST PRACTICES Best Practice: ensure that complex password are used for sa and other sql-server-specific logins. Think about ENFORCE EXPIRATION & MUST_CHANGE for any new SQL login
  • 18. use specific logins Best Practice: use different accounts for different sql-server oriented services Component Windows Server 2008 Windows 7 and Windows Server 2008 R2 and higher Recommended accounts Database Engine NETWORK SERVICE Virtual Account * SQL_Engine SQL Server Agent NETWORK SERVICE Virtual Account * SQL_Agent SSAS NETWORK SERVICE Virtual Account * SQL_srvAS SSIS NETWORK SERVICE Virtual Account * SQL_srvIS SSRS NETWORK SERVICE Virtual Account * SQL_srvRS SQL Server Distributed Replay Controller NETWORK SERVICE Virtual Account * SQL_DRContro SQL Server Distributed Replay Client NETWORK SERVICE Virtual Account * SQL_DRReplay FD Launcher (Full-text Search) LOCAL SERVICE Virtual Account SQL Server Browser LOCAL SERVICE LOCAL SERVICE SQL Server VSS Writer LOCAL SYSTEM LOCAL SYSTEM SECURITY BEST PRACTICES
  • 19. sysadmin membership • Member of sysadmin fixed-server role can do whatever they want on SQL Server • by default sysadmin fixed-server role has CONTROL SERVER permission granted explicity • do not explicitly grant CONTROL SERVER for Windows logins, Windows Group logins and SQL logins SECURITY BEST PRACTICES Best Practice: carefully choose the membership of sysadmin fixed-server
  • 20. general administration • everything (almost always) works under sa account especially with CONTROL SERVER permission • institute dedicated Windows logins for DBAs, and assign these logins sysadmin rights on SQL Server for administration purposes. SECURITY BEST PRACTICES Best Practice: use built-in fixed server roles and database roles or create your custom roles, then apply for specific logins
  • 21. revoke guest access • by default guest accounts exist in every user and system databases • is a potential security risk in lock down environment • those accounts could be targets for attackers • asssign public server role membership if you will need explicit access to user databases SECURITY BEST PRACTICES Best Practice: disable all gueast user access from all user and system databases (excluding msdb database)
  • 22. limit public permission • SQL Server has many Stored Procedures and many od them have public access permission: • OLE AUTOMATION: sp_OACreate, sp_OAGetProperty, sp_OAStop, sp_OAMethod, sp_OAGerErrorInfo, sp_OADestroy, sp_OASetProperty • REGISTRY ACCESS: xp_regremovemultistring, xp_regaddmultistring, xp_regread, xp_regdeletekey, xp_regdeletevalue, xp_regwrite • OTHER ROUTINES: sp_sdidebug, xp_logevent, sp_sprintf, xp_dsninfo, xp_msver, sp_sscanf, xp_stopmail, xp_grantlogin, xp_eventlog, xp_dirtree SECURITY BEST PRACTICES Best Practice: revoke public role access for some axtended procedures and check other store procedures
  • 23. hardening sql server ports • default sql server port 1433/1434 is well known as standard target for hackers • by using SQL Server Configuration Manager you: • can change default port • can use specific TCP port intead of dynamic • remeber about similar TCP/UDP ports (1433, 1434) SECURITY BEST PRACTICES Best Practice: change default SQL Server port if it’s possible
  • 24. disable sql server browser • by default SQL Server Browser is disabled • tt’s necessary to run when multiple instances are running on a single server • any Windows user having the following rights would be capable to run the SQL Server Browser service: • deny access to this computer from the network / deny logon locally / deny logon as a batch job • Deny logon through Terminal Services / log on as a service / read and write the SQL Server registry keys related to network communication (ports and pipes) SECURITY BEST PRACTICES Best Practice: change default SQL Server port if it’s possible
  • 25. secure service accounts • different service accounts for different services • dedicated low-privileges domain accounts • check membership on a regular basis • use strong and different passwords for each account SECURITY BEST PRACTICES Best Practice: create good plan and make note about service accounts and passwords
  • 26. 3 | SQL Server 2014 Security Enhacements
  • 27. transparent data encryption • first introduced with SQL Server 2008 • protecting data by performing I/O encryption and decryption for database and log files • passphrase (less secure), asymmetric key (strong protection, poor performance), symmetric key (good performance, strong enough protection), certificate (strong protection, good performance) • New functionality for backup: • takes non-encrypted backup data • encrypt data before writing to disk • compression is performed on the backup data first • then encryption is applied to compressed data • support for backup to Azure SQL14 SECURITY ENHACEMENTS
  • 28. encryption key management • Encryption options include: • encryption algorithm • certificate or asymmetric key • only asymmetric key reside in EKM is supported • multiple algorithm up to AES-256 are supported • manageable by PowerShell, SMO, SSMS, T-SQL • VERY IMPORTANT: • asymmetric key or certificate MUST be backed up • location MUST be different than backup location • No RESTORE without asymmetric key or certificate SQL14 SECURITY ENHACEMENTS
  • 29. connect any database • new server-level permission • grant CONNECT ANY DATABASE to a login that must connect to all databases currently exist and any new in future • does not grant any parmission in any database beyond connect • to allow an auditing process to view all data or all database states CONNECT ANY DATABASE may be combined with: • SELECT ALL USER SECURABLES • VIEW SERVER STATE SQL14 SECURITY ENHACEMENTS
  • 30. impersonate any login • new server-level permission • when granted IMPERSONATE ANY LOGIN allows a middle-tier process to impersonate the account of clients connecting to it • when denied IMPERSONATE ANY LOGIN a high privileged login can be blocked from impersonating other logins • example: CONTROL SERVER permission can be blocked from impersonating other logins SQL14 SECURITY ENHACEMENTS
  • 31. select all user securables • new server-level permission • when granted SELECT ALL USER SECURABLES a login (for example for auditing purposes) can view data in all databases that the user can connect to SQL14 SECURITY ENHACEMENTS
  • 32. SQL Server Express Security • by default: • instance name: SQLExpress • networking protocol: disabled • sql server browser: disabled • user (local) instances: • separated instance generated from parent instance • sysadmin privileges on SQL Express on local machine • runs as user process not as service process • only windows logins are supported • RANU instance (run as normal user)
  • 33. 4 | SQL Server Security In The Cloud
  • 34. Cloud Security Microsoft Cloud Security Approach in a Nutshell • Principles, patterns, and practices • Security engineering • Threats and countermeasures • Secure the network, host, and application • Application scenarios and solutions • Security frame • People, process, and technology • Application, infrastructure, and business http://bit.ly/1zmeYi2
  • 35. Security Model • uses regular sql security model • authenticate logins, map to users and roles • authorize users and roles to sql objects • support for standard sql auth logins • username + password • {admin, administrator, guest, root, sa} Security model is 100% compatible with on-premise SQL
  • 36. Security Requirements for Azure Platform Microsoft Azure Datacenters • North America • North-central US - Chicago, IL • South-central US - San Antonio, TX • West US - California • East US - Virginia • Asia • East Asia - Hong Kong, China • South East Asia – Singapore • South America • Brasil – Sao Paulo • Europe • North Europe - Dublin, Ireland • West Europe - Amsterdam, Netherlands • Japan • Japan East, the Tokyo area • Japan West, the Kansai area • Oceania (announced, coming soon) • Sydney, New South Wales • Melbourne, Victoria
  • 37. Security Requirements for Azure Platform • As a Service Provider Microsoft has an obligation to passing the several rules for security: • ISO 27001/27002 Audit and Certification • SOC 1/SSAE 16/ISAE 3402 and SOC 2 Attestations • Cloud Security Alliance (CSA) Cloud Controls Matrix (CCM) • Payment Card Industry (PCI) Data Security Standards (DSS) Level 1
  • 38. Security Requirements for Azure Platform Also they passing (…) several data securing audits: • Australian Government Information Security Registered Assessors Program (IRAP) • United Kingdom G-Cloud Australian Government IRAP • Multi-Tier Cloud Security Standard for Singapore (MTCS SS 584:2013) • HIPAA Business Associate Agreement (BAA) • EU Model Clauses • Food and Drug Administration 21 CFR Part 11 • Family Educational Rights and Privacy Act (FERPA) • Federal Information Processing Standard (FIPS) 140-2 • Trusted Cloud Service Certification developed by China Cloud Computing Promotion and Policy Forum (CCCPPF) • Multi-Level Protection Scheme (MLPS)
  • 39. Security Requirements for Azure Platform ISO/IEC 27001:2005 Audit and Certification ISO Scope: The following Azure features are in scope for the current ISO audit: Cloud Services (including Fabric and RDFE), Storage (Tables, Blobs, Queues), Virtual Machines (including with SQL Server), Virtual Network, Traffic Manager, Web Sites, BizTalk Services, Media Services, Mobile Services, Service Bus, Workflow, Multi-Factor Authentication, Active Directory, Right Management Service, SQL Database, and HDInsight. This includes the Information Security Management System (ISMS) for Azure, encompassing infrastructure, development, operations, and support for these features. Also included are Power BI for Office 365 and Power Query Service. SOC 1 and SOC 2 SSAE 16/ISAE 3402 Attestations Scope: The following Azure features are in scope for the current SOC 1 Type 2 and SOC 2 Type 2 attestations: Cloud Services (includes stateless Web, and Worker roles), Storage (Tables, Blobs, Queues), Virtual Machines (includes persistent virtual machines for use with supported operating systems) and Virtual Network (includes Traffic Manager).
  • 40. Security Requirements for Azure Platform And of course requirements for Data Centers: • Physical security of the data centers (locks, cameras, biometric devices, card readers, alarms) • Firewalls, application gateways and IDS to protect the network • Access Control Lists (ACLs) applied to virtual local area networks (VLANs) and applications • Authentication and authorization of persons or processes that request access to data • Hardening of the servers and operating system instances • Redundant internal and external DNS infrastructure with restricted write access • Securing of virtual machine objects • Securing of static and dynamic storage containers
  • 41. SQL Server 2005 {9.0} NON-Compability • Common Language Runtime (CLR) and CLR User-Defined Types • Database Mirroring • Service Broker • Table Partitioning • Typed XML and XML indexing is not supported. The XML data type is supported by SQL Azure.
  • 42. SQL Server 2008 {10.0} NON-Compability • Change Data Capture • Data Auditing • Data Compression • Extended Events • External Key Management / Extensible Key Management • FILESTREAM Data • Integrated Full-Text Search • Large User-Defined Aggregates (UDAs) • Large User-Defined Types (UDTs) • Performance Data Collection (Data Collector) • Policy-Based Management • Resource Governor • SQL Server Replication • Transparent Data Encryption
  • 43. SQL Server 2008 R2 {10.50} NON-Compability • SQL Server Utility • SQL Server PowerShell Provider • Master Data Services SQL Server Management Studio does not support Windows Azure SQL Database in versions prior to SQL Server 2008 R2
  • 45. SQL Server Security in the Cloud • Same security principals like SQL Server on premise • Full responsibility for DBA with Virtual Machine • Partial responsibility for DBA with Azure SQL Database • Automatic updates for Azure SQL Database • New functionality implemented by Microsoft • Some incompabilities with t-sql, functions, store procedures • Increased security by default on Azure platform
  • 46. SQL Server in Cloud: WASD vs VM Choose Azure SQL Database, if: • You are building brand new, cloud-based applications; or you want to migrate your existing SQL Server database to Azure and your database is not using one of the unsupported functionalities in Azure SQL Database. For more information, see Azure SQL Database Transact-SQL Reference. This approach provides the benefits of a fully managed cloud service and ensures the fast time-to-market. • You want to have Microsoft perform common management operations on your databases and require stronger availability SLAs for databases. This approach can minimize the administration costs and at the same time provides a guaranteed availability for the database. Choose SQL Server in Azure VM, if: • You have existing on-premises applications and wish to stop maintaining your own hardware or you consider hybrid solutions. This approach lets you get access to high database capacity faster and also connects your on-premises applications to the cloud via a secure tunnel. • You have existing IT resources, need full administrative rights over SQL Server, and require the full compatibility with on-premises SQL Server (for example, some features do not exist in Azure SQL Database). This approach lets you minimize costs for development or modifications of existing applications with the flexibility to run most applications. In addition, it provides full control on the VM, operating system, and database configuration.
  • 47. Three Pillars of a Secure Hybrid Cloud Environment • Pillar One: risk assessment and management • A definition of the risks that apply to various asset(s), based on their business criticality. • An assessment of the current status of each risk before it’s moved to the cloud. Using this information, each risk can be accepted, mitigated, transferred or avoided. • An assessment of the risk profile of each asset, assuming it has been moved to the cloud. • Pillar Two: policy and compliance • Cloud providers need to understand that simply listing compliance certifications isn’t sufficient. In line with the mantra of transparency explored in the previous point, providers should take a proactive stance to sharing their security implementations and controls. Dimension Data often assists clients by providing them with a list of questions that we believe they should be posing to cloud providers as part of the evaluation process, to ensure they’re covering all the bases.’
  • 48. Three Pillars of a Secure Hybrid Cloud Environment • Pillar Three: provider transparency • Governance: the ability of an organisation to govern and measure enterprise risk introduced by cloud. • Legal issues: regulations, and requirements to protect the privacy of data, and the security of information and computer systems. • Compliance and audit: maintaining and proving compliance when using the cloud. • Information management and data security: managing cloud data, and responsibility for data confidentiality, integrity and availability. • Portability and interoperability: the ability to move data or services from one provider to another, or bring them back in-house. • Business continuity and disaster recovery: operational processes and procedures for business continuity and disaster recovery.
  • 49. Three Pillars of a Secure Hybrid Cloud Environment • Pillar Three: provider transparency • Data centre: evaluating any elements of a provider’s data centre architecture and operations that could be detrimental to ongoing services. • Incident response, notification and remediation: adequate incydent detection, response, notification, and remediation. • Application security: securing application software running on or developed in the cloud. • Encryption and key management: identifying proper encryption usage and scalable key management. • Identity and access management: assessing an organisation’s readiness to conduct cloud- based identity, entitlement, and access management. • Virtualisation: risks associated with multi-tenancy, virtual machine isolation and co- residence, hypervisor vulnerabilities, etc.
  • 50. Recommendations • Create a new role for an Information Manager who owns information governance across (all SharePoint) environments • Train and educate all stakeholders about risk and liability • Assess the appropriateness of using SharePoint versus other document management tools • Define information governance policies for access, retention, archival, and backup • Automate risk controls • Audit user and data activities • Resources: • Microsoft TechNet • Microsoft MSDN • Legal Sources for Compliance Requirements
  • 52. links • ISECOM (the Institute for Security and Open Methodologies) • http://www.isecom.org/about-us.html • OSSTMM (Open Source Security Testing Methodology Manual) • http://www.isecom.org/research/osstmm.html • Library of Resources for Industrial Control System Cyber Security • https://scadahacker.com/library/index.html • patterns & practices: Cloud Security Approach in a Nutshell • https://technet.microsoft.com/en-us/ff742848.aspx • Microsoft Azure Trust Center: Security • http://azure.microsoft.com/en-us/support/trust-center/security/ • 10 Things to know about Azure Security • https://technet.microsoft.com/en-us/cloud/gg663906.aspx • Security Best Practice and Label Security Whitepapers • http://blogs.msdn.com/b/sqlsecurity/archive/2012/03/07/security-best-practice-and-label-security-whitepapers.aspx
  • 53. links • Hello Secure World • http://www.microsoft.com/click/hellosecureworld/default.mspx • SQL Server Label Security Toolkit • http://sqlserverlst.codeplex.com/ SQL Server Best Practices Analyzer • Microsoft Baseline Configuration Analyzer 2.0 • http://www.microsoft.com/en-us/download/details.aspx?id=16475 • SQL Server 2005 Best Practices Analyzer (August 2008) • http://www.microsoft.com/en-us/download/details.aspx?id=23864 • Microsoft® SQL Server® 2008 R2 Best Practices Analyzer • http://www.microsoft.com/en-us/download/details.aspx?id=15289 • Microsoft® SQL Server® 2012 Best Practices Analyzer • http://www.microsoft.com/en-us/download/details.aspx?id=29302
  • 54. links • Microsoft Security Assessment Tool • http://www.microsoft.com/downloads/details.aspx?FamilyID=6D79DF9C-C6D1-4E8F-8000- 0BE72B430212&displaylang=en • Microsoft Application Verifier • http://www.microsoft.com/downloads/details.aspx?FamilyID=bd02c19c-1250-433c-8c1b- 2619bd93b3a2&DisplayLang=en • Microsoft Threat Analysis & Modelling Tool • http://www.microsoft.com/downloads/details.aspx?FamilyID=59888078-9daf-4e96-b7d1- 944703479451&DisplayLang=en • How To: Protect From SQL Injection in ASP.NET • http://msdn2.microsoft.com/en-us/library/ms998271.aspx • Securing Your Database Server • http://msdn.microsoft.com/en-us/library/aa302434.aspx • Threats and Countermeasures • http://www.microsoft.com/technet/security/guidance/serversecurity/tcg/tcgch00.mspx
  • 55. links • Configure Windows Service Accounts and Permissions • https://msdn.microsoft.com/en-us/library/ms143504.aspx#Network_Service • Select an Account for the SQL Server Agent Service • https://msdn.microsoft.com/en-us/library/ms191543.aspx • Server Configuration - Service Accounts • https://msdn.microsoft.com/en-us/library/cc281953.aspx
  • 56. azure resources: security • Azure Security: Technical Insights • Security Best Practices for Developing Azure Solutions • Protecting Data in Azure • Azure Network Security • Microsoft Antimalware for Azure Cloud Services and Virtual Machines • Microsoft Enterprise Cloud Red Teaming • Microsoft Azure Security and Audit Log Management • Security Management in Microsoft Azure • Crypto Services and Data Security in Azure
  • 57. azure resources: security & privacy • Business Continuity for Azure • Understanding Security Account Management in Azure • Azure Data Security: Cleansing and Leakage • Scenarios and Solutions Using Azure Active Directory Access Control • Securing and Authenticating a Service Bus Connection • Azure Privacy Overview (PDF) • Azure Privacy Statement • Law Enforcement Request Report • Protecting Data and Privacy in the Cloud
  • 58. azure resources: compliance & more • Response to Cloud Security Alliance Cloud Controls Matrix (DOC) • Azure HIPAA Implementation Guidance (PDF) • Azure Customer PCI Guide (PDF) • The Microsoft Approach to Cloud Transparency (PDF) • Microsoft Trustworthy Computing • Operational Security for Online Services Overview (PDF) • Data Classification for Cloud Readiness • CISO Perspectives on Data Classification (PDF) • An Introduction to Designing Reliable Cloud Services (PDF) • Deploying Highly Available and Secure Cloud Solutions (PDF)
  • 59. azure resources RESOURCE DESCRIPTION MSDN: Azure SQL Database MSDN: SQL Server in Azure Virtual Machines Azure.com: Azure SQL Database Links to the library documentation. Azure SQL Database and SQL Server -- Performance and Scalability Compared and Contrasted This article explains performance differences and troubleshooting techniques when using Azure SQL Database and SQL Server running on- premises or in a VM. Application Patterns and Development Strategies for SQL Server in Azure Virtual Machines This article discusses the most common application patterns that apply to SQL Server in Azure VMs and also hybrid scenarios including Azure SQL Database. Microsoft Enterprise Library Transient Fault Handling Application Block This library lets developers make their applications running on Azure SQL Database more resilient by adding robust transient fault handling logic. Transient faults are errors that occur because of some temporary condition such as network connectivity issues or service unavailability. Since Azure SQL Database is a multitenant service, it is important to handle such errors to minimize any application downtime.
  • 60. credits • Yes, 123456 is the most common password, but here’s why that’s misleading http://arstechnica.com/security/2015/01/yes-123456-is-the-most-common-password-but-heres-why-thats-misleading/ • CIO’s are Listening, Security is Important… https://communities.intel.com/community/itpeernetwork/blog/2014/05/20/cio-s-are-listening-security-is-important
  • 61. after session CONTACT: • MAIL: KoprowskiT@windowslive.com • SOCIAL MEDIA: facebook, twitter, linkedin, xing SLIDES FROM SESSION: • SlideShare Profile: http://www.slideshare.net/Anorak • SQL Relay Site: http://www.sqlrelay.co.uk BLOGS: • ITPRO Anorak’s Vision: http://itblogs.pl/notbeautifulanymore/ [PL/EN] • Volume Licensing Specialites: http://koprowskit.eu/licensing/ [PL] • My MVP Blog: http://koprowskit.eu/geek/ [EN/ES/RU/NL/PL]