Связаться с нами Facebook Linkedin Youtube

SDS | Software Development Security

  • Продолжительность
    5дн/40часов
  • Направление
    ИТ Безопасность

 

Course program:

Section 1: Introduction to Secure Software Development Lifecycle

 

  1. Secure Systems Development Lifecycle (Secure SDLC).
  2. SDLC models (SAMM, BSSIMM, Microsoft).
  3. SDLC practices for Agile:
    1. Trainings.
    2. Governance and metrics.
    3. Policies.
    4. Security Requirements Definitions.
    5. Quality gates/Bug bars.
    6. Security and Privacy risk assessments and reviews.
    7. Design requirements.
    8. Attack surface analysis and reviews.
    9. Threat modeling.
    10. Safe development tools.
    11. Unsafe functions.
    12. Secure coding guidelines.
    13. Static analysis.
    14. Dynamic analysis.
    15. Fuzz testing.
    16. Incident response planning.
    17. Secure configuration guidelines.
    18. Operational security practices.
    19. Secure SDLC implementation guidelines.
    20. Writing good use cases and abuse cases.
    21. Putting the right priorities.

 

Section 2: JavaScript and Web security.

 

  1. JavaScript security model.
  2. Same-origin policy.
  3. Frame sandboxing.
  4. Content security policy.
  5. Cross-origin security sharing.
  6. JavaScript signing.
  7. Web-workers security.
  8. Differences in the browser implementations of security features.
  9. Common vulnerabilities:
    1. Cross-Site Scripting.
    2. Reflected XSS.
    3. Stored XSS.
    4. DOM XSS.
    5. Universal XSS (Flash, etc.).
    6. Vulnerable components (JavaScript libraries, Browser plugins).
    7. Lack of CSRF tokens.
    8. Lack of authentication for Ajax requests.
    9. Java applet exploits.
    10. Weak SOP configuration.
    11. Weak SSL protection. SSL stripping. Man in the middle attacks.
    12. Insecure server headers.
    13. Insecure cookie flags.
    14. Insecure WebSockets.
    15. Privacy issues (geolocation, video recording, microphone access).
    16. Click-jacking.
    17. Unsafe coding practice: innerHTML, document.write, eval.
    18. Insecure session management. Session fixation. Weak session timeouts.
    19. Unsafe URL redirects.
    20. SQL injections.
    21. XML and Xpath injections.
    22. Other injections (LDAP, OS command, etc.).
    23. Business logic flaws.
    24. Concurrency and race conditions issues.
    25. Unsafe deserialization.
    26. Unsafe signatures (hash extension attacks).
    27. DDoS attacks and defenses.
    28. SOAP and REST services security.
    29. Metadata leak.
    30. Backup files.
    31. Social engineering attacks and protection measures.
    32. Password policies and account management.
    33. Admin interfaces.
    34. Improper error handling.
    35. Hardcoded credentials.
    36. Directory traversal.

 

Section 3: .NET and C# security.

 

  1. Managed code.
  2. .NET runtime.
  3. .NET security model.
  4. App domains.
  5. Windows security architecture.
  6. Privileges.
  7. Access rights.
  8. ACL management. Null DACL.
  9. Service security groups.
  10. Integrity levels.
  11. Delegation and impersonalization.
  12. Declarative and imperative application permissions.
  13. Class security.
  14. XSS protection.
  15. CSRF tokens.
  16. SQL injection protection.
  17. SSL.
  18. Authentication and authorization.
  19. Cryptography functions.
  20. Weak random number generators.
  21. Secure password and key storage.
  22. Auditing and logging.
  23. Viewstate signing.
  24. Unsafe reflection.
  25. Number overflow handling.
  26.  Unsafe native libraries and memory corruption vulnerabilities.
  27. Unsafe array access.
  28. Safe resource permissions (file system, registry, mutexes, etc.).
  29. Secure interprocess communication.
  30. Code signing.
  31. DLL hijacking.
  32. Certificate PINNING.
  33. Thread safety mechanisms.
  34. Obfuscation.
  35. Security of active browser components.
  36. Windows Firewall.
  37. IPv6 support note.
  38. Secure service communication with desktop.
  39. CardSpace.

 

Section 4: Java specifics

 

  1. Java Virtual Machine (JVM) and Java Runtime Environment (JRE).
  2. ByteCode Verifier and Classloader;
  3. Security Manager and Access Controller, managing permissions policy.
  4. Java Native Interface (JNI).
  5. Secure Sockets Layer (SSL).
  6. Code signing.
  7. Integer overflow. CVE-2013-1493.
  8. Unsafe deserialization CVE 2008-5353.
  9. Unsafe reflection CVE-2004-2331.
  10. Unsafe inner classes.
  11. CERT coding guidelines.
  12. Oracle coding guidelines.

 

Section 5: Android specifics

 

  1. Android security architecture.
  2. SELinux.
  3. Android permissions.
  4. Unix security (process, user, filesystem).
  5. Dalvik.
  6. ART.
  7. Dex file format.
  8. SQL injection for content providers.
  9. Activity hijacking.
  10. Broadcast Theft.
  11. Service hijacking.
  12. Broadcast injection.
  13. Insecure pending intents.
  14. Dos null check.
  15. Intent injection.
  16. Log injection.
  17. Weak randomness generators.
  18. OWASP TOP10 mobile risks for Android.
  19. Unofficial markets.

 

 

Section 6 iOS specifics

 

  1. iOS security architecture.
  2. IOS Secure Coding guide.
  3. iOS sandbox.
  4. iOS permissions.
  5. iOS DRM.
  6. UIWebView risks.
  7. Mach file format.
  8. Keyboard caching.
  9. Insecure URL handlers.
  10. SQL injections.
  11. Keychain.
  12. UDID leaks.
  13. OWASP top 10 mobile risks for iOS.

 

Section 7. Software protection

 

  • Mobile application protection techniques for Android and iOS. Rooting detection, protections from static and dynamic analysis.