How to Lose Your Job in 3 Easy Steps Robert L Davis Database Engineer @SQLSoldier www.sqlsoldier.com How to Lose Your Job in 3 Easy Steps
Agradecimiento a los patrocinadores Premium Silver Personal
Robert L Davis @SQLSoldier PASS Security Virtual Chapter Microsoft Certified Master Data Platform MVP @SQLSoldier www.sqlsoldier.com Database Engineer BlueMountain Capital Management 17+ years working with SQL Server PASS Security Virtual Chapter http://security.sqlpass.org Volunteers needed Database Engineer at BlueMountain Capital Management Foremer Principal Database Architect at DB Best Technologies www.dbbest.com Former Principal DBA at Outerwall, Inc Former Sr. Product Consultant with Idera Software Former Program Manager for SQL Server Certified Master program in Microsoft Learning Former Sr. Production DBA / Operations Engineer at Microsoft (CSS) Microsoft Certified Master: SQL Server 2008 / MCSM Charter: Data Platform Co-founder of the SQL PASS Security Virtual Chapter MCITP: Database Developer: SQL Server 2005 and 2008 MCITP: Database Administrator: SQL Server 2005 and 2008 MCSE: Data Platform MVP 2014 Co-author of Pro SQL Server 2008 Mirroring Former Idera ACE (Advisors & Community Educators) 2 time host of T-SQL Tuesday Guest Professor at SQL University, summer 2010, spring/summer 2011 Speaker at SQL PASS Summit 2010, 2011, and 2012 including a pre-con in 2012 Speaker/Pre-con at SQLRally 2012 17+ years working with SQL Server Writer for SQL Server Pro (formerly SQL Server Magazine) Member: Mensa Dog picture: Maggie and Woody SQLCruise instructor: Seattle to Alaska 2012 Speaker at SQL Server Intelligence Conference in Seattle 2012 Blog: http://www.sqlsoldier.com Twitter: http://twitter.com/SQLSoldier
How to Lose Your Job in 3 Easy Steps 3 Mistakes …
How to Lose Your Job in 3 Easy Steps 3 Mistakes … That many DBAs make
How to Lose Your Job in 3 Easy Steps 3 Mistakes … That many DBAs make And some developers too
How to Lose Your Job in 3 Easy Steps 3 Mistakes … That many DBAs make And some developers too That could and should cost you your job
How to Lose Your Job in 3 Easy Steps 3 Mistakes … That many DBAs make And some developers too That could and should cost you your job That cause lost data, lost revenue, and lost customers
How to Lose Your Job in 3 Easy Steps
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges DBAs are the guardians of the data
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges DBAs are the guardians of the data Cannot protect the data if you do not control it
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges DBAs are the guardians of the data Cannot protect the data if you do not control it Permissions requests should be needed (not desired) and justifiable
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges DBAs are the guardians of the data Cannot protect the data if you do not control it Permissions requests should be needed (not desired) and justifiable Anything else adds risk
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks:
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations Fines and penalties from government agencies
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations Fines and penalties from government agencies Loss of customers
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations Fines and penalties from government agencies Loss of customers Loss of public standing / Public relations issues
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations Fines and penalties from government agencies Loss of customers Loss of public standing / Public relations issues Loss of company credit rating
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Risks: Data loss or theft Performance problems because of bad user queries Violation of governmental compliancy regulations Fines and penalties from government agencies Loss of customers Loss of public standing / Public relations issues Loss of company credit rating Imprisonment
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Principle of Least Privilege
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Principle of Least Privilege Only the lowest level of permissions required and justified are granted
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Principle of Least Privilege Only the lowest level of permissions required and justified are granted If you grant permissions to someone, you had better be able to say why it was required and why it was justified
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Principle of Least Privilege Only the lowest level of permissions required and justified are granted If you grant permissions to someone, you had better be able to say why it was required and why it was justified If something bad happens, the DBA will be the person held responsible for giving away too many permissions
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Principle of Least Privilege Only the lowest level of permissions required and justified are granted If you grant permissions to someone, you had better be able to say why it was required and why it was justified If something bad happens, the DBA will be the person held responsible for giving away too many permissions The person who did the bad thing may be help responsible as well, but to a lesser degree than the DBA
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Final thought
How to Lose Your Job in 3 Easy Steps 3. Giving elevated privileges Final thought It’s a lot easier to give limited permissions straight away than to reduce the permissions later
How to Lose Your Job in 3 Easy Steps
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read Three settings for Page Verification:
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read Three settings for Page Verification: CHECKSUM (default since SQL Server 2005)
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read Three settings for Page Verification: CHECKSUM (default since SQL Server 2005) TORN_PAGE_DETECTION (default in SQL Server 2000)
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read Three settings for Page Verification: CHECKSUM (default since SQL Server 2005) TORN_PAGE_DETECTION (default in SQL Server 2000) NONE (has never been the default)
How to Lose Your Job in 3 Easy Steps 2. Disabling Page Verification Page verification detects corruption when page is read Three settings for Page Verification: CHECKSUM (default since SQL Server 2005) TORN_PAGE_DETECTION (default in SQL Server 2000) NONE (has never been the default) If anyone changes setting to none, that person should be fired
How to Lose Your Job in 3 Easy Steps
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data This means more than just having backups
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data This means more than just having backups Ensuring backups are restorable (test your backups)
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data This means more than just having backups Ensuring backups are restorable (test your backups) Recovering from a disaster while meeting data loss (RPO) and downtime (RTO) requirements
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data This means more than just having backups Ensuring backups are restorable (test your backups) Recovering from a disaster while meeting data loss (RPO) and downtime (RTO) requirements
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups DBAs number one priority Again, you are the guardian of the data This means more than just having backups Ensuring backups are restorable (test your backups) Recovering from a disaster while meeting data loss (RPO) and downtime (RTO) requirements Practice restore scenarios so that you know what to do when disaster strikes Store backups separate from the server
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups If you inherit a server with databases on it, the first and last thing you should do is backups
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups If you inherit a server with databases on it, the first and last thing you should do is backups First make sure backups are happening and all databases are being backed up
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups If you inherit a server with databases on it, the first and last thing you should do is backups First make sure backups are happening and all databases are being backed up Next attend to other important things
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups If you inherit a server with databases on it, the first and last thing you should do is backups First make sure backups are happening and all databases are being backed up Next attend to other important things Lastly, find out the RPO and RTO requirements and adjust your backups as needed
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RPO: Recovery Point Objective
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RPO: Recovery Point Objective How much data is the business willing to lose in the event of a disaster?
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RPO: Recovery Point Objective How much data is the business willing to lose in the event of a disaster? Your potential for data loss = the last time a backup ran
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RPO: Recovery Point Objective How much data is the business willing to lose in the event of a disaster? Your potential for data loss = the last time a backup ran RPO = the minimum frequency of your backups
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RTO: Recovery Time Objective
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RTO: Recovery Time Objective How long can the business be down in the event of a disaster?
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RTO: Recovery Time Objective How long can the business be down in the event of a disaster? In a worst case scenario, how long do you have to get the databases restored and operational again
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RTO: Recovery Time Objective How long can the business be down in the event of a disaster? In a worst case scenario, how long do you have to get the databases restored and operational again RTO dictates the restore plan for getting databases restored to meet this requirement
How to Lose Your Job in 3 Easy Steps 1. Lack of good backups RTO: Recovery Time Objective How long can the business be down in the event of a disaster? In a worst case scenario, how long do you have to get the databases restored and operational again RTO dictates the restore plan for getting databases restored to meet this requirement The restore plan dictates what backup plan needs to be implemented
How to Lose Your Job in 3 Easy Steps Apologies! I apologize for the misleading title If you came to learn how to get fired, but you actually learned how to keep your job! Q & A
Thank you for attending! ¡Gracias! Thank you for attending! My blog: www.sqlsoldier.com Twitter: twitter.com/SQLSoldier Whitepaper: 5 DBA Mistakes That Can Cost You Your Job: https://www.idera.com/resourcecentral/whitepapers/5-dba-mistakes-that-can-cost-you-your-job