Skip to content

Pattern idea: Secure InnerSource #369

Closed
@spier

Description

@spier

A question came up in Slack about how to practice InnerSource in a secure way.

I am summarizing the conversation here, removing any names of people/companies to comply with Chatham House Rule.

The question was:

My company is trying to adopt an InnerSource model.
Our security team is not comfortable with opening up source code internally. They are worried that it would lead to code leaks.

What should we do to reduce the associated risk?

Definition code leak in this context:
A bad employee may get the code and expose it on the Internet.
This could negatively impact company branding or have other negative impacts on the company, depending on what was leaked and the industry the company is in.

Naming ideas for a possible pattern

  • Secure InnerSource
  • Security and InnerSource
  • Satisfying Security Concerns
  • Addressing Security Concerns
  • Security Concerns and Mitigation
  • Working with Security
  • Security and Transparency
  • Security and Discoverability
  • Secure Discoverability
  • Discoverability in a Secure Way

Metadata

Metadata

Assignees

No one assigned

    Labels

    1-initialDonuts, Early pattern ideas, ... (Please see our contribution handbook for details)📖 Type - Content WorkWorking on contents is the main focus of this issue / PR

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions