comment on

In my experience this sort of setup is not at all unusal when you're dealing with sensitive data. I've implemented this sort of thing. I've also recommended this kind of solution where the security issues required it.

Keeping the more secure info on completely separate box, database, etc. protects your most sensitive data even if the first box is compromised.

While this makes implementation harder (keeping chucks of database in sync, etc.) the issue is security - not ease of implementation :-)

Whether this is sensible for your particular situation depends on the risk assessment of the info in question becoming public.... so it may well be overkill. It's not completely stupid tho'.

In reply to Re: Twin interfaces, and one and a half databases to a project by adrianh
in thread Twin interfaces, and one and a half databases to a project by JPaul

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks