Dear Pete-
In your original question -
How to securely store credit cards to make them safe in case of a system penetration.
Don't forget the low tech, Kevin Mitnick style, social engineering. If you get enough credit cards, as previously noted, you become an attractive target.
Consider:
- Who has physical access to any system that has these numbers?
- Are the passwords written on the monitor?
- Where and how secure are your backups?
- Are there operators who have been warned against sneaky people calling up seeking "help"?
- Is the server room decently locked up?
- Does just anyone have the ablity to come and go?
- How good is the security of the back end that clears the transactions?
- Do you actively patrol the security updates for the OS?
Sometimes the fancy lock pick is a crow bar.
-Diskcrash
-
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.
|
