Orphaned pages

From Guidance Share

Jump to: navigation, search

Showing below up to 100 results starting with #51.
View (previous 100) (next 100) (20 | 50 | 100 | 250 | 500).

  1. Encrypt sensitive data if you need to store it
  2. Encrypt the contents of the authentication cookies.
  3. Encrypt the data or secure the communication channel.
  4. Engineering Practices Overview
  5. Ensure database connections are always closed
  6. Fail securely
  7. Firewall restrictions
  8. Guidance
  9. Guidance Overview
  10. How To: Delay Sign an Assembly in .NET 2.0
  11. How To: Perform a Security Code Review Review for Managed Code (Baseline Technique)
  12. How To: Use SecureString in .NET 2.0
  13. Impersonate original caller only when required
  14. Install URLScan on your Web server
  15. Keep unencrypted data close to the algorithm.
  16. Limit session lifetime.
  17. Log detailed error messages.
  18. Log key events.
  19. Login account configuration
  20. Logon auditing
  21. Maintain sensitive data on the server
  22. Maintain separate administration privileges.
  23. Make sure that users do not bypass your checks.
  24. News and Highlights
  25. Partition your Web site
  26. Personas at patterns & practices
  27. Place Web controls and user controls in separate assemblies
  28. Place resource access code in a separate assembly
  29. Protect authentication cookies.
  30. Protect credentials and authentication tickets
  31. Protect log files.
  32. Protect sensitive data in storage
  33. Protect sensitive data over the wire
  34. Protect session state from unauthorized access.
  35. Protect the credentials for SQL authentication
  36. Protect view state with MACs
  37. Protect your administration interfaces.
  38. Protect your configuration store.
  39. Protect your encryption keys.
  40. Require authentication for sensitive pages
  41. Require strong passwords.
  42. Resources Index
  43. Restrict the application in the database
  44. Restrict unauthorized callers
  45. Restrict unauthorized code
  46. Restrict user access to system-level resources.
  47. Retrieve sensitive data on demand.
  48. Sanitize Input
  49. Secure UDL files with restricted ACLs
  50. Secure restricted pages with SSL
  51. Secure sensitive data over the network
  52. Secure the authentication cookie
  53. Secure the session data
  54. Secure your connection strings
  55. Security Tech Centers
  56. Separate public and restricted areas.
  57. Set the correct character encoding
  58. Software Engineering Practices Overview
  59. Store password hashes with salt
  60. Support password expiration periods.
  61. Tech Centers
  62. Technologies
  63. Test1
  64. Test page 1
  65. Test page g
  66. Test page g2
  67. Threat Model
  68. Trap and log ADO.NET exceptions
  69. Use Data Protection API (DPAPI) for encrypting secrets.
  70. Use Escape Routines
  71. Use File authorization with Windows authentication
  72. Use Page.ViewStateUserKey to counter one-click attacks
  73. Use Parameter Batching
  74. Use Programmatic Impersonation
  75. Use Regular Expressions for Input Validation
  76. Use SSL effectively
  77. Use SSL to protect session authentication cookies.
  78. Use URL Authorization
  79. Use URL authorization for page and directory access control
  80. Use Windows authentication
  81. Use a generic error page in your ASP.NET applications
  82. Use absolute URLs for navigation
  83. Use account lockout policies for end-user accounts.
  84. Use explicit role checks for fine-grained authorization
  85. Use least privileged accounts
  86. Use least privileged process and service accounts.
  87. Use multiple gatekeepers.
  88. Use principal demands on classes and methods
  89. Use secure credential management
  90. Use separate data access assemblies
  91. Use server-side input validation
  92. Use stored procedures
  93. Use the ASP.NET validateRequest option
  94. Use the HttpOnly cookie option
  95. Use the correct algorithm and correct key size.
  96. Use the frame security attribute
  97. Use the innerText property
  98. Use type safe SQL parameters
  99. Validate HTML Controls
  100. Validate Input

View (previous 100) (next 100) (20 | 50 | 100 | 250 | 500).

Views
Personal tools