Giter Site home page Giter Site logo

Comments (6)

warrenrjwc avatar warrenrjwc commented on July 1, 2024

What is the intention of this suggestion? I am not clear on what we want to use this for. Is this a suggested use case?

from documentation.

MitchellJThomas avatar MitchellJThomas commented on July 1, 2024

My intention is to create discussion about establishing and maintaining trust in a system critical to operations, mainly to reach clarity around whether the architecture provides or requires those trust components. Ignoring this we run the risk of designing a vulnerable system.

from documentation.

adammontville avatar adammontville commented on July 1, 2024

It's a good idea to look at this.

from documentation.

JasonKeirstead avatar JasonKeirstead commented on July 1, 2024

I think we need to be a bit careful about getting into the weeds here. Not all cybersecurity operation stacks run in a zero trust model nor would we want to suggest that should even be required.... it would immediately limit the applicability of our work to only those organizations who are embracing such a model, which are still somewhat rare. Also, this is very application-stack specific. Two systems in the architecture may secure their communication channel many different ways.

from documentation.

adammontville avatar adammontville commented on July 1, 2024

I agree that we don't want to be so forward looking that we lose the ability to transition. Perhaps there's still something we can glean from looking at a zero trust architecture. Are there decisions we could make to day that would hinder embracing that model in the future? Are there base components in a zero trust architecture that are prevalent enough today to consider including/assuming?

from documentation.

sparrell avatar sparrell commented on July 1, 2024

I agree we should be looking at the question "how do you secure OCA systems?" As the original point made is valid that security systems are prime target. I agree with the comment that there are different ways to do this and different needs for different use cases and different legacy architectures. I recommend against getting too prescriptive too soon. We might want to start by gathering examples of how you could do OCA system security. And we should look at all aspects. Personally I'd start with some recursive aspects of the system feeding itself especially in any proof of concept. E.g. drink our own champagne

from documentation.

Related Issues (18)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.