Note that there are some explanatory texts on larger screens.

plurals
  1. POHide private keys etc from administrators
    primarykey
    data
    text
    <p>Currently I take part in developing a system based on Java EE (WebLogic server, to be more precise) and I am wondering how to protect some private data from administrators. For example, some parts of a system stores credentials for legacy systems in a deployment descriptors as plain text and this is bad because a deployer can read application configuration file (<code>ejb-jar.xml</code>, for example) and steal username and password for powerfull account. I want to close this security hole, but don't know how.</p> <p>Now I am interested in protecting this kind of data:</p> <ol> <li>Login</li> <li>Password</li> <li>Private key for symmetric encryption</li> </ol> <p>From <a href="http://kingsfleet.blogspot.com/2008/12/storing-password-somewhere-safe.html" rel="nofollow">here</a> I've discovered that I can use a JCEKS keystore to protect this type of information, but I can not understand how to use it. My application still should contain the kestore password and the key password to access it. So, a depoyer can steal passwords for keystores and keys, find my secure storage and steal credetials. Obviously, I can revoke <code>read</code> privileges from the deployer account, but then he can decompile my appliaction and develop his own similar app (or edit my one), that simply prints secure data to some file or send it by email... And now I am stuck... </p> <p>Can anybody give me some links that can explain how to protect a system from administrators? Weblogic related links will be preferable. I totally understand that it is not possible to protect from all administrators and there should be some <code>security administrator</code> that will be responsible for keystore management and so forth, but I want to secure all sensitive data from everybody else.</p> <p><strong>RESULTS</strong> </p> <p>Both <em>jtahlborn</em>'s and <em>slim</em>'s answers are correct, but <em>slims</em>'s answer in more interesting. I think that in my case it will be appropriate to accept only signed applications for installation on the server. This decidion can solve problem with applicatoin modifications done by a administrator. Administrators will have password from keystore and all keys, but they will not have access to keystore file at all. Access to keystore file will have only special security administrators ('rw') and server ('r'). So, everybody will have the key, but nobody (except security administrators) will have access to the box.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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