Secure Coding Practices

Code that holds up against injection, broken access control and stolen sessions: a team standard, safe defaults for queries, output and secrets, and review habits that make security part of every change.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Secure Coding Practices, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Secure Coding Practices

Writing code that resists common attacks such as injection and broken authentication, with security checks built into everyday development.

  1. Attack surface map of the code you own
  2. Two-page secure coding standard for the team
  3. Hardcoded secrets removed and rotated
  4. Parameterised queries across every data access path
  5. Input validation at every trust boundary
  6. Output encoding to shut out cross-site scripting
  7. Password storage and login flow check
  8. Server-side permission check on every endpoint
  9. Safe error handling and security event logging
  10. Security checklist in the pull request template
  11. Weekly review slot for high-risk changes
  12. Lightweight threat modelling for new features
  13. Security champion role on the team
  14. Rotation schedule for keys used by your code
  15. Monthly review of security event logs
  16. Permission matrix kept current as endpoints change
  17. Security bug backlog with fix-by dates
  18. Monthly vulnerable code walkthrough for the team
  19. Yearly revision of the secure coding standard
  20. OWASP Top 10 mapped to your own code
  21. Practice lab with a deliberately vulnerable app
  22. Session and token handling fundamentals
  23. Using cryptography libraries correctly
  24. Server-side request forgery defences
  25. Safe file upload and parser handling
  26. Cross-site request forgery and SameSite cookies
  27. Writing abuse-case tests alongside features
  28. Content Security Policy and security headers rollout
  29. Build or buy decision for user authentication
  30. Rate limiting and brute-force protection on login
  31. Multi-factor authentication for user accounts
  32. Banned dangerous functions list
  33. Secure-by-default helpers for common tasks
  34. Personal data and secrets kept out of logs
  35. Preparing for an external penetration test
  36. Remediation sprint after a penetration test report
  37. Pre-launch security review for a new product
  38. Vulnerability report response drill
  39. Secure development answers for customer questionnaires
  40. Secure coding basics in a new engineer's first month
  41. Security assessment of an inherited codebase
  42. Minimum security for a solo engineer at a startup
  43. Security in the team's definition of done
  44. Reviewing AI-generated code for security flaws
  45. Security acceptance of code handed over by an agency
  46. Tenant isolation enforced in the data layer
  47. Business logic abuse and race condition cases
  48. Security review of an OAuth or SSO integration
  49. Memory safety plan for native code components
  50. Variant analysis after a vulnerability is fixed

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Attack surface map of the code you own

Most teams can list their public pages but not the admin routes, webhook receivers, file importers, queue consumers and debug endpoints that also accept input from outside. Mapping every place untrusted data enters your code tells you where the next six months of security effort should go, and it is the first thing a penetration tester will ask for.

First tasks

  • Export the full route list from each service's router
  • Add webhooks, queue consumers, file imports and scheduled jobs that read external data
  • Mark each entry point with its audience and whether it touches money or personal data
  • Raise tickets for endpoints that should not exist or lack authentication

Two-page secure coding standard for the team

Long security policies are written once and never read, while a short standard with ten concrete rules gets quoted in code review. Agreeing the rules your team will hold each other to, with a good and a bad code example for each in your own language, gives reviewers something specific to point at instead of a vague feeling.

First tasks

  • List the five worst security bugs your team has shipped or nearly shipped
  • Draft one rule per bug class with a correct and incorrect code sample
  • Review the draft with the team and cut any rule nobody can check in review
  • Publish the standard beside the contributing guide and link it from the PR template

Hardcoded secrets removed and rotated

Hardcoded API keys, database passwords and signing secrets in source code or committed config files end up in every clone, every CI log and every laptop backup. Finding them, moving them into a secret store or environment injection, and rotating each one that was ever committed closes one of the cheapest routes into your systems.

First tasks

  • Run a secret search across the whole git history of each repository
  • List each finding with its owner system and whether it is still valid
  • Move live secrets into the secret store and update the code to read them
  • Rotate every secret that was ever committed and log the rotation date

Make it yours.

Install Secure Coding Practices, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.