Home

Open source is enormous, and new releases, bug fixes, and patches are released on a daily basis. It is hard for any company to keep pace of all the changes that occur in the open source world. As a result, we've identified five Be-Secure Open source tech stacks or blue prints, which we refer to as Be-Secure environments, to assist the Be-Secure community in assessing the security of these open source projects.

• Type of Be-Secure environments.

1.  DO [Environments which include DevOps & infra tools]

The DevOps environment is concerned with all types of open source tools used in DevOps and how they might be secured both in terms of source code and implementation. This would allow users to use secure DevOps technologies to implement DevSecOps. The security vulnerabilities in the listed DevOps tools will be investigated and remedied.

2.  L&F [Environments for language and framework specific tool chains]

The language and framework environment is concerned with all open source programming languages and frameworks that are used to construct diverse applications. In this environment these programming languages will be evaluated, and their flaws will be addressed.

3.  A [Environments for Application Specific tool chains ]

Environment is involved with all open source software and how it might be safeguarded.

4.  DA [Environments handle Multiple distributed environments)]

All open source distributed applications and blockchain frameworks are the emphasis of this environment.

Detailed description about each environments and corresponding ansible playbooks are added under upcoming pages

• Demo On Setting up of a O31E lab in a Box a.k.a BeS Lab Box

• Demo an environments playbooks