Open mylamour opened 6 years ago
包含了设计原则,配置,从开发到部署,一系列的web端服务端客户端的安全检查列表
AUTHENTICATION SYSTEMS (Signup/Signin/2 Factor/Password reset)
- [x] Use HTTPS everywhere. 但是有ssltrip和sslsplit
- [ ] Store password hashes using
Bcrypt
(no salt necessary -Bcrypt
does it for you). 目前看来是无解的吧?Bcrypt无解?- [ ] Destroy the session identifier after
logout
.
确定一个用户Session对应唯一ID,设置过期时间- [ ] Destroy all active sessions on reset password (or offer to).
登录注册重置确认邮件,总之确认唯一session,就是用户现在的有效session But MITM, And Phising OK?- [ ] Must have the
state
parameter in OAuth2. 框架虽然都完善了这些个功能,但是开发者不一定使用,还要记得callback的redirect_uti校验是否允许,否则会导致泄露- [ ] No open redirects after successful login or in any other intermediate redirects.
- [ ] When parsing Signup/Login input, sanitize for javascript://, data://, CRLF characters. 有序列化就需要反序列化,不在序列化的过程中出现漏洞,就有可能在反序列化的过程中出现漏洞。那么多库,不可能没有问题。
- [ ] Set secure, httpOnly cookies. Chrome Plugin get it
- [ ] In Mobile
OTP
based mobile verification, do not send the OTP back in the response whengenerate OTP
orResend OTP
API is called. 避免本地校验和硬编码,OTP(One Time Password)
[ ] Limit attempts to Login
, Verify OTP
, Resend OTP
and generate OTP
APIs for a particular user. Have an exponential backoff set or/and something like a captcha based challenge.
有的验证码绑定一个session....可怕不,手机验证码不要只有数字,可以在几分钟内暴力猜出来
[ ] Check for randomness of reset password token in the emailed link or SMS.
[ ] Set an expiration on the reset password token for a reasonable period.
[ ] Expire the reset token after it has been successfully used.
my cart
, my history
should check the logged in user's ownership of the resource using session id.
见过一个写的代码居然把用户密码作为cookie存储本地,真是气人
/me/orders
instead of /user/37153/orders
. This acts as a sanity check in case you forgot to check for authorization token.
防暴力猜解
Edit email/phone number
feature should be accompanied by a verification email to the owner of the account.
还要在后端验证提交的数据格式是不是邮箱格式,手机格式,一切对服务器来说是输入的地方就有危险,不要依靠前端的过滤。
Profile photo upload
feature should sanitize all the EXIF
tags also if not required.
图片马。
IDATA CHUNCK
里面可以写php webshell,图像上传是任何一个网站都具有的功能,但是校验不好就坏了,记得要二次渲染。
UUID
instead of integers. You can find an implementation for this for your language on Github.暂时不是很懂
salt
from payment gateways should not be hardcoded.secret
/ auth token
from 3rd party SDK's should not be hardcoded.server to server
should not be done from the app.Add
CSP header to mitigate XSS and data injection attacks. This is important.
至关重要
Add
CSRF header to prevent cross site request forgery. Also add SameSite attributes on cookies.Add
HSTS header to prevent SSL stripping attack.Add
your domain to the HSTS Preload ListAdd
X-Frame-Options to protect against Clickjacking.Add
X-XSS-Protection header to mitigate XSS attacks.有进就有出,有序列化就需要反序列化
- [ ]
Sanitize
all user inputs or any input parameters exposed to user to prevent XSS.- [ ] Always use parameterized queries to prevent SQL Injection.
- [ ] Sanitize user input if using it directly for functionalities like CSV import.
- [ ]
Sanitize
user input for special cases like robots.txt as profile names in case you are using a url pattern like coolcorp.io/username.- [ ] Do not hand code or build JSON by string concatenation ever, no matter how small the object is. Use your language defined libraries or framework.
- [ ] Sanitize inputs that take some sort of URLs to prevent SSRF.
- [ ] Sanitize Outputs before displaying to users.
创业企业都喜欢用云,但是安全意识不足,又很容易出问题。
open ports
.
如无必要,白名单端口放行。
databases
especially MongoDB & Redis.
不要暴露在外网,也不要把密码写在纸上贴在电脑前。。。
有一份awsome ssh config是比较安全的配置,可以搜索一下
及时更新,打补丁。做好应急响应,要有Plan B.确保发生事情时按原计划进行。不慌不忙,尽快溯源。
开debug报错会泄露敏感信息,做好异常处理的同时,线上永远不要开debug
log everthing you can log, store it, backup it . analysis it.
burp插件商店里有aws安全检查
权限分级,异常监控。
- [ ] Set up an email (e.g. security@coolcorp.io) and a page for security researchers to report vulnerabilities.
- [ ] Depending on what you are making, limit access to your user databases.
- [ ] Be polite to bug reporters.
- [ ] Have your code review done by a fellow developer from a secure coding perspective. (More eyes)
- [ ] In case of a hack or data breach, check previous logs for data access, ask people to change passwords. You might require an audit by external agencies depending on where you are incorporated.
- [ ] Set up Netflix's Scumblr to hear about talks about your organization on social platforms and Google search.
这是一份OWASP TOP10变更对比,不过注入始终是NO.1,多出来个XXE,把错误配置,和授权绕过排名提高关注。 作为第一次阅读OWASP 的白皮书,除了系统化一下整个概念流程之后,个人觉得比较好的是最后的几个提问,比较值得思考(不要自己看着什么就是是是,要想一想):
而我自己主要作为一个安全研发,和web渗透测试,比较关注前两个问题。
What’s Next for Developers
What’s Next for Security Testers
RISK计算
Other
前期搞日站技术,和机器学习技术。后期搞SDL,安全架构,。 美亚,绿盟,启明星辰的股票都在涨啊...只能看看模拟盈亏ing.