Security should be on the forefront of every data professionals' mind. It doesn't matter if you are developer, administrator, or other position, you ought to be considering the security implications of changes you make to the database. More and more data is being stored in databases, and often it's moved between databases as well. Whether that's to data warehouses, or development environments, we ought to be considering security to be more a part of our daily work and process rather than something limited to specific systems.
Vendors are trying to make systems more secure. I see the encryption capabilities grow with each version of SQL Server, and new features have been added, like TDE, to help technology professionals secure their data. Other vendors have introduced other safety mechanisms, and one caught my eye by claiming to be "hack resistant". It's the ZenithVault database says it is practically impossible for hackers to gain access to storage systems and steal confidential information. It supposedly does this by "data splitting", moving parts of data onto separate servers.
It sounds like a good solution, in the same way that TDE is a good solution. If someone is able to access your physical files, they won't be able to read the data in them. That's a good precaution, and it works well in TDE's case (I can't speak for ZenithVault), but it's also not hack resistant.
The biggest hacking problem that I see in the world today is SQL Injection. Since legitimate accounts can access your database, often through web-based front ends, and SQL Injection uses these same accounts to access data, none of the encryption and security capabilities you set up protect you. None of these items come into play when you have code that allows hackers to inject their own commands through your existing application, web based or not.
Secure coding is important, and it's something that we should all require and practice as we build software. Your application might not access secure data today, but that might change in the future.