Skip to main content

How safe are your secrets?


We’ve all have service accounts, application accounts, sysadmin and domain admin accounts and other privileged shared accounts on our systems. These are all vital to the running of our applications and databases.
But do you keep them safe?
Are the passwords held somewhere secure, do you audit who looks them up, do you change them regularly, do you even know if these passwords are correct?

I recently installed Thycotic’s Secret Server for that purpose.
This is a web app with a SQL backend that can hold all of your passwords, control who can view or edit them, audit who has viewed or changed them, can run a regular heartbeat to check that the password in the database is correct, auto change the passwords and update related services at the same time.

If you have a third party that needs to access a server or application but you don’t want them to know the password they use, then you can configure an account with a launcher where they can click on the icon and it logs in to the system without them needing to see or do anything. And it can record what they do once they are on that system as well.

We hold Windows, SQL, Oracle, Unix, web accounts but it can be configured to manage lots more as well as mundane  things like combination codes.
It has full DR and HA capability – vital for something that holds all the information your would need in a disaster and it even has a Blackberry and iPhone app giving it extra flexibility, though we haven’t tried these yet.

I have been very pleased with Secret Server for enterprise password management and would certainly recommend them and the teams that I’ve rolled it out to here have been equally impressed with it.


Take a look at www.thycotic.com

Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…