<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 29, 2018, at 9:21 AM, Carl Myers <<a href="mailto:cmyers@cmyers.org" class="">cmyers@cmyers.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">It depends so much on your threat model and what you are trying to accomplish...<br class="">this is my biggest pet peve about security. People do things because some<br class="">website or resource says "this is secure" but they have no clue why. If you<br class="">want to secure something, the first thing you have to do is figure out what you<br class="">are securing it AGAINST. Guess what? You can have 100% foolproof unhackable<br class="">security for your server, just disconnect it from the internet, turn it off,<br class="">bury it in a deep grave in a field somewhere where nobody will ever find it.<br class="">But that isn't very helpful is it?<br class=""><br class="">A threat model outlines what threats you care about, and what threats you don't.<br class="">For example, let's say I deem it possible someone has a way to use a bug in<br class="">apache tomcat (the application server my service uses in this example) to<br class="">execute remote code, how would I deal with that? Well, I could have the<br class="">application server run as an unprivileged user and harden things further with<br class="">SELinux and other techniques to try to minimize the damage such a user can do.<br class="">What if someone is capable of breaking encryption (P = NP)? I consider that<br class="">highly unlikely, and if someone could do that the security of my application is<br class="">my last concern (oh no, my bitcoin!)<br class=""><br class="">So the first step to security, IMO, is to decide what class of attackers you<br class=""></div></div></blockquote> ^^^^^^^^^^. The way I was taught is that the first step is to estimate the value of what it is you are trying to protect. That way, you invest in security in proportion to the value of what is at risk. So, one might invest less in security to protect a LAN file server containing recent newspaper photos than one would use to protect a bank wire transfer server.</div><div><br class=""></div><div>I realize the thread was started as a learning vehicle so it might be useful to consider security as a spectrum of possibilities ranging from basic prudent practice up to extreme hardening (with probably a decrease in ease of use and access).</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">care about, what they are capable of, and then how to best mitigate those<br class="">attacks.<br class=""></div></div></blockquote><div><br class=""></div></div><div class="">
--<br class="">Mark Weisler <br class="">PGP Key ID 0x9E358F7B<br class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">PGP Key fingerprint </span>5969 3C77 AB25 B398 9E84 3FB5 0C30 D913 9E35 8F7B</div>
</div>
<br class=""></body></html>