Loading...
Please wait, while we are loading the content...
Similar Documents
Secure hash algorithm (sha)-1 to (2008).
| Content Provider | CiteSeerX |
|---|---|
| Abstract | Even though the vulnerability countshave dropped, the number of vulner-abilities is not zero. And, even in my wildest dreams, I do not think we will get to zero. I will explain why shortly. In the very early days of the SDL, Microsoft focused heavily on removing design and code-level security vulnerabili-ties; as we progressed, we added processes that help reduce the chance that new vul-nerabilities get added to the software. Examples of implementation require-ments in the SDL include: • Use of code analysis tools on develop-er’s desktops to find security vulnera-bilities. • Removing known insecure functions (such as the C runtime strcpy and strncpy functions). • Migrating weak cryptographic algo-rithms to more robust algorithms |
| File Format | |
| Publisher Date | 2008-01-01 |
| Access Restriction | Open |
| Subject Keyword | Secure Hash Algorithm Implementation Require-ments New Vul-nerabilities Get Robust Algorithm Code Analysis Tool Early Day Develop-er Desktop Sdl Include Code-level Security Vulnerabili-ties Weak Cryptographic Algo-rithms Strncpy Function Known Insecure Function Runtime Strcpy Vulnerability Countshave Security Vulnera-bilities |
| Content Type | Text |
