Skip to content

Secure Development Policy

This Secure Development Policy establishes guidelines and requirements for secure software development practices at Code Town, Inc. (D/B/A “Shorebird”). It aims to integrate security throughout the software development lifecycle (SDLC) to minimize vulnerabilities and protect company and customer data.

This policy applies to all employees, contractors, and third parties involved in software development activities.

These following policy statements outline our approach to integrating security from initial design through deployment and ongoing maintenance.

Security must be integrated into every phase of the SDLC, including requirements gathering, design, implementation, testing, and deployment.

All developers must use company-approved development tools and platforms. Multi-factor authentication is enabled for all development accounts to prevent unauthorized access.

Development environments must be isolated from production data to minimize the risk of data breaches.

All software developed must follow secure coding standards to prevent common vulnerabilities such as SQL injection, cross-site scripting (XSS), and buffer overflows. To maintain high standards:

  • Implement input validation for all data inputs
  • Use parameterized queries to prevent SQL injection
  • Implement proper error handling without revealing sensitive information
  • Apply the principle of least privilege in code implementation

All code changes must:

  • Be reviewed before merge, with a specific focus on security, by a reviewer other than its author: our automated code reviewer, or a person
  • Be approved by a person when the change was written by an AI agent
  • Pass static code analysis and automated tests before being merged
  • Address all high and critical security issues identified during review or analysis

Reviewing every change catches security issues early.

Developers are responsible for writing and running unit tests that cover security functionality. Integration tests should include scenarios that verify security controls are working as expected.

Use version control systems for all source code. Implement branch protection rules to prevent direct commits to main branches. Regularly audit repository access and remove outdated permissions.

Ensure that sensitive information such as API keys, passwords, and certificates are never committed to the repository. Use environment variables or secure secret management systems to handle sensitive data.

Code we run in CI can read our source and secrets, so we keep it few and fixed:

  • Prefer GitHub’s or our own actions, or a short script, to a third-party action
  • Pin every action to a full-length commit SHA, never a tag or branch, which its owner can move. An organization setting rejects workflows whose actions are not pinned
  • Pin reusable workflows the same way, except where a registry requires a tag ref; each such exception is approved as described under Compliance and Enforcement
  • Update pins through reviewed changes, opened by Dependabot with a cooldown of several days where it is configured (security fixes are not delayed)

Security considerations extend to the deployment process:

  • Use automated, repeatable deployment processes to minimize human error
  • Implement separation of duties between development and deployment
  • Use immutable infrastructure where possible to ensure consistency

Regularly review and update our deployment processes to align with industry best practices and emerging threats.

Compliance with this policy is mandatory for all employees, contractors, and third parties with access to Shorebird’s data.

In rare cases, business needs, local laws, or regulations may require exceptions. Management will approve any exceptions and define alternative solutions.

Non-compliance may lead to disciplinary action, including termination, as per Shorebird’s policies.

This policy will be reviewed annually or when significant changes occur to maintain its continuing suitability, adequacy, and effectiveness.

Reviews must consider changes in the regulatory landscape.