Ensure that your scripts are secure
The dangers of scripting are well known, and vulnerabilities are discovered with increasing regularity. As such, it's of ethical benefit for authors to ensure all code used regularly passes security processes.
Criteria: Script security
Check the code for vulnerabilities, exploits, header issues, and code injection.
Resources
- 5 Ways to Keep Your website from Getting Hacked
- Content Security Policy Reference
- Frontend Security Checklist
- GPF - General Policy Framework (PDF) - 1.7 - Strategy (Encryption)
- GR491 - 1-7020 - Data Security
- Hacksplaning
- How OWASP Helps You Secure Your Full-Stack Web Applications
- How To Prevent WordPress SQL Injection Attacks
- OWASP Top Ten
- Script Integrity
- Security Headers
- Security Headers using meta
- The Basics of Web Application Security
- The OWASP Top 10
- United Nations SDGS - Goal 3 - Health & Well-being
- United Nations SDGS - Goal 16 - Sustainable Society
- United Nations SDGS - Goal 17 - Global Partnership
- Web security
- Website security
- WordPress Security: How to Protect Your website from Attacks and Hackers
Impact: Medium, Effort: Medium
| GRI | Impact |
|---|---|
| materials | Medium |
| energy | Medium |
| water | Medium |
| emissions | Medium |
Benefits of this guideline
- Environment: Websites that have no outstanding security issues are less likely to become a target for individuals who might exploit them (consuming vast amounts of data in the process).
- Security: Having a secure website can prevent personal information from being exploited.
- Performance: A secure website is less likely to have its infrastructure breached, which could lead to vast amounts of data being stolen, corrupted, or destroyed.
- Economic: Preventing security issues will help your project and visitors avoid financial crime.
Example
-
contentThis article has information and examples of XSS security issues to avoid.
Tags:
- JavaScript
- Privacy
- Security
- Social Equity