---
title: "Secure Development Policy"
canonical_url: "https://flowfuse.com/handbook/company/security/secure-development/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# Secure Development Policy

<table>
<thead>
  <tr>
    <th>
      Policy owner
    </th>
    
    <th>
      Effective date
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      @knolleary
    </td>
    
    <td>
      2023-05-01
    </td>
  </tr>
</tbody>
</table>

## Purpose

To ensure that information security is designed and implemented within the
development lifecycle for applications and information systems.

## Scope

All FlowFuse applications and information systems that are business critical
and/or process, store, or transmit Confidential data. This policy applies to all
internal and external engineers and developers of FlowFuse software and
infrastructure.

## Secure Development Policy

FlowFuse policy requires that:

1. FlowFuse software engineering and product development is required to follow
security best practices. Product should be "Secure by Design" and "Secure by
Default".
2. Quality assurance activities must be performed as part of the routine development
process. This includes, but not limited to:
  - suitable unit testing included with any change request,
  - peer code reviews prior to merging changes,
  - continual automated testing
  - manual product testing and verification prior to release to production

Code reviews should also cover documentation and tests to ensure our
[definition of done](https://flowfuse.com/handbook/engineering/project-management#defining-done) is
achieved.

1. Risk assessment activities (i.e. threat modeling) must be performed for a
new product or major changes to an existing product.
2. Security requirements must be defined, tracked, and implemented.
3. Security analysis must be performed for any open source software and/or
third-party components and dependencies included in FlowFuse software products.
4. Static application security testing (SAST) must be performed throughout
development and prior to each release.
5. Dynamic application security testing (DAST) must be performed prior to each
release.
6. All critical or high severity security findings must be remediated prior to
each release.
7. All critical or high severity vulnerabilities discovered post release must
be remediated in the next release or within the defined, predetermined timeframe.
8. Any exception to the remediation of a finding must be documented and
approved by the CTO.

## Secure Development Environment

FlowFuse uses separate Staging and Production systems. These are logically
segregated environments in different AWS accounts.

The Production environment is classified Critical with suitable controls in place
to limit access to the infrastructure.

---

Policy derived from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates) ([CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)) and [Vanta](https://vanta.com)

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
