Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Only to a limited degree. </p> <p>If they are administering the actual SQL Server Instance as well they have the "keys to the kingdom". They can view the definitions of every object, make changes to the definitions or the data, and do virtually anything else. Even if they merely have admin rights on the machine but not the server, they can get admin on the server through certain <a href="http://www.mssqltips.com/sqlservertip/2682/recover-access-to-a-sql-server-instance/" rel="nofollow">techniques</a> which are generally considered valid rather than bugs or exploits. It is after all their server and the server will obey them.</p> <p>In a situation like this, you need to be able to trust those admins at least to a degree. If you cannot trust them, you should ideally not be hosting with them at all, and if you can't trust them and must host with them, try to get your own VM where you can at least apply some additional security and auditing.</p> <p>There are a few things you can do though, but none are completely effective.</p> <p>The first is encryption. If you meet all the requirements and set it up properly, SQL's transparant data encryption can prevent an admin without the keys from reading the data (but they can still see the structure!) in the database. This is quit effective at protecting the actual data (but not the structure) but is difficult to set up properly.</p> <p>You can use the "with encryption" option to protect your stored procedures. This is very weak protection and its very easy to get around this. But it at least sends a strong message to the curious that you don't want them looking and makes them jump through some hoops.</p> <p>Traces and auditing will also help you determine what happened and see if they did anything, but those come at a performance price.</p>
    singulars
    1. This table or related slice is empty.
    1. POSecuring a SQL Server database on a server administered /controlled by third party admins
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTimothyAWiseman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSecuring a SQL Server database on a server administered /controlled by third party admins
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COIf the information you're worried about is controlled by U.S. government regulation (such as PHI covered under HIPAA) then the basic encryption algorithms in SQL server meet the requirements assuming you keep the decryption keys securely stored elsewhere. Otherwise, like the answer states, it's their server and they have a fair amount of control over it that you simply cannot avoid.
      singulars
      1. PO
      1. USBen Finkel
    2. COYou can also identify key fields that need to be encrypted, such as passwords, SSNs, salaries, etc... and encyrpt/decrypt them in your application level prior to sending that data to the SQL server.
      singulars
      1. PO
      1. USBen Finkel
    3. CO@BenFinkel That is a great point. Thanks for adding it.
      singulars
      1. PO
      1. USTimothyAWiseman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload