Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's no easy answer to a broad question like this. There are many different kinds of threats that your application could encounter - what one generally needs to do called <em><a href="http://msdn.microsoft.com/en-us/library/ff648006.aspx" rel="nofollow noreferrer">threat modeling</a></em>, consisting of:</p> <ul> <li>identifying vulnerabilities</li> <li>identifying attack vectors</li> <li>identifying possible countermeasures</li> </ul> <p>Before you can make decisions about whether to use SSL, HTTPS, encryption or any other technology, you need to understand what threats each mitigates and how they can be compromised.</p> <p>While there are best practices for security, you can't just follow a recipe to secure a system.</p> <p>While, in general, you mention some reasonable countermeasures for securing an application (password hashing, HTTPS) the devil is in the details. You sometimes have to consider scenarios like:</p> <ul> <li><strong>replay attacks</strong> (where message traffic is recorded and replayed)</li> <li><strong>denial of service attacks</strong> (where your server is bombarded with malformed or invalid messages in an attempt to overload it)</li> <li><strong>man-in-the-middle</strong> (attacks in which the attacker intercepts or alters messages in route)</li> </ul> <p>There are many other attack vectors (and possible countermeasures) to consider. How much effort you expend depends on the importance of the resource being protected, the consequences if it's compromised, and your level of skill and understanding of the security environment you will operate in.</p> <p>Microsoft has published something called the <a href="http://www.microsoft.com/security/sdl/resources/faq.aspx" rel="nofollow noreferrer">Security Development Lifecycle (SDL)</a>, which you may want to look into. There's also an entire <a href="http://msdn.microsoft.com/en-us/library/ff648032.aspx" rel="nofollow noreferrer">Security Engineering</a> section on MSDN that has lots of background and guidance on this topic.</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.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      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