- The Guide to Finding and Reporting Web Vulnerabilities
- About the Author
- About the Tech Reviewer
- Foreword
- Introduction
- Who This Book Is For
- What Is In This Book
- Happy Hacking!
- 1 Picking a Bug Bounty Program
- 2 Sustaining Your Success
- 3 How the Internet Works
- 4 Environmental Setup and Traffic Interception
- 5 Web Hacking Reconnaissance
- 6 Cross-Site Scripting
- 7 Open Redirects
- 8 Clickjacking
- 9 Cross-Site Request Forgery
- 10 Insecure Direct Object References
- 11 SQL Injection
- 12 Race Conditions
- 13 Server-Side Request Forgery
- 14 Insecure Deserialization
- 15 XML External Entity
- 16 Template Injection
- 17 Application Logic Errors and Broken Access Control
- 18 Remote Code Execution
- 19 Same-Origin Policy Vulnerabilities
- 20 Single-Sign-On Security Issues
- 21 Information Disclosure
- 22 Conducting Code Reviews
- 23 Hacking Android Apps
- 24 API Hacking
- 25 Automatic Vulnerability Discovery Using Fuzzers
Prevention
It’s difficult to completely prevent sensitive information leaks. But you can reliably lower the possibilities of information disclosure by safeguarding your data during the development process.
完全阻止敏感信息泄露是困难的。但你可以通过在开发过程中保护数据,可靠地降低信息泄露的可能性。
The most important measure you should take is to avoid hardcoding credentials and other sensitive information into executable code. Instead, you can place sensitive information in separate configuration files or a secret storage system like Vault ( https://github.com/hashicorp/vault/ ). Also, audit your public code repositories periodically to make sure sensitive files haven’t been uploaded by accident. Tools can help you monitor code for secrets, such as secret-bridge ( https://github.com/duo-labs/secret-bridge/ ). And if you have to upload sensitive files to the production server, apply granular access control to restricts users’ access to the files.
你应该采取的最重要的措施是避免将凭据和其他敏感信息硬编码到可执行代码中。相反,可以将敏感信息放在单独的配置文件或像 Vault(https://github.com/hashicorp/vault/)这样的秘密存储系统中。另外,定期审核公共代码库,以确保敏感文件没有被意外上传。工具可以帮助您监视包含秘密的代码,例如 secret-bridge(https://github.com/duo-labs/secret-bridge/)。如果您必须上传敏感文件到生产服务器,则应用精细的访问控制以限制用户对文件的访问。
Next, remove data from services and server responses that reveals technical details about the backend server setup and software versions. Handle all exceptions by returning a generic error page to the user, instead of a technical page that reveals details about the error.
接下来,要从服务和服务器响应中移除透露后端服务器设置和软件版本的技术细节数据。处理所有异常情况时,向用户返回通用的错误页面,而不是一个透露错误详细信息的技术页面。
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论