base on Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale. 🚀 _[Portals for Mac](https://github.com/build-trust/ockam/blob/develop/examples/app/portals/README.md) – A macOS app built in Swift that uses the Ockam Rust library to privately share a service on your Mac with anyone, anywhere. The service is shared securely over an end-to-end encrypted and mutually authenticated Ockam Portal. Your friends will have access to it on their *localhost*! This app is a great example of the kinds of things you can build with Ockam_ [👉](https://github.com/build-trust/ockam/blob/develop/examples/app/portals/README.md) --- <a href="https://discord.gg/RAbjRr3kds"><img alt="Discord" src="https://img.shields.io/discord/1074960884490833952?label=Discord&logo=discord&style=flat&logoColor=white"></a> [](https://repo-rater.eddiehub.io/rate?owner=build-trust&name=ockam) # Trust for Data-in-Motion Ockam is a suite of open source programming libraries and command line tools to orchestrate end-to-end encryption, mutual authentication, key management, credential management, and authorization policy enforcement – at massive scale. Modern applications are distributed and have an unwieldy number of interconnections that must trustfully exchange data. To trust data-in-motion, applications need end-to-end guarantees of data authenticity, integrity, and confidentiality. To be private and secure by-design, applications must have granular control over every trust and access decision. Ockam allows you to add these controls and guarantees to any application. ## Quick Start Let's build a solution for a very common secure communication topology that applies to many real world use cases. We'll build our first example using [Ockam Command](https://docs.ockam.io/reference/command), but it is just as easy to build end-to-end trustful communication using [Ockam Programming Libraries](https://docs.ockam.io/reference/libraries/rust). An application service and an application client running on two private networks wish to securely communicate with each other without exposing ports on the Internet. In a few simple commands, we’ll make them safely talk to each other through an End-to-End Encrypted Cloud Relay. ## Install Ockam Command If you use Homebrew, you can install Ockam using brew. ```bash # Tap and install Ockam Command brew install build-trust/ockam/ockam ``` This will download a precompiled binary and add it to your path. If you don’t use Homebrew, you can also install on Linux and MacOS systems using curl. ```bash curl --proto '=https' --tlsv1.2 -sSfL https://install.command.ockam.io | bash ``` ### End-to-end encrypted and mutually authenticated communication Next, step through the following commands to setup secure and private communication between our application service and an application client. ```bash # Check that everything was installed correctly by enrolling with Ockam Orchestrator. # # This will create a Space and Project for you in Ockam Orchestrator and provision an # End-to-End Encrypted Cloud Relay service in your `default` project at `/project/default`. ockam enroll # -- APPLICATION SERVICE -- # Start an application service, listening on a local IP and port, that clients would access # through the cloud encrypted relay. We'll use a simple HTTP server for this first example # but this could be any other application service. python3 -m http.server --bind 127.0.0.1 6000 # In a new terminal window, setup a tcp-outlet that makes a TCP service available at the given # address `6000`. We can use this to send raw TCP traffic to the HTTP server on port `6000`. # Finally create a relay in your default Orchestrator project. Relays make it possible to # establish end-to-end protocols with services operating in remote private networks, without # requiring a remote service to expose listening ports to an outside hostile network like the # Internet. ockam tcp-outlet create --to 6000 ockam relay create # -- APPLICATION CLIENT -- # Setup a local tcp-inlet to allow raw TCP traffic to be received on port `7000` before # it is forwarded. A TCP inlet is a way of defining where a node should be listening for # connections, and where it should forward that traffic to. ockam tcp-inlet create --from 7000 # Access the application service, that may be in a remote private network though # the end-to-end encrypted secure channel, via your private and encrypted cloud relay. curl --head 127.0.0.1:7000 ``` ### Private and secure by design In the example above, we’ve created two nodes and established an end-to-end secure channel between them through an encrypted cloud relay. For the sake of simplicity, we ran both ends on a single machine, but they could also be run on completely separate machines with the same result: an end-to-end encrypted and mutually authenticated secure channel. Distributed applications that are connected in this way can communicate without the risk of spoofing, tampering, or eavesdropping attacks, irrespective of transport protocols, communication topologies, and network configuration. As application data flows across data centers, through queues and caches, via gateways and brokers - these intermediaries, like the cloud relay in the above example, can facilitate communication but cannot eavesdrop on, or tamper with data. You can establish secure channels across networks and clouds over multi-hop, multi-protocol routes to build private and secure by design distributed applications that have a small vulnerability surface and full control over data authenticity, integrity, and confidentiality. ### Trust for data-in-motion Behind the scenes, the above commands generated unique cryptographically provable identities and saved corresponding keys in a vault. Your orchestrator project was provisioned with a managed credential authority, and every node was setup to anchor trust in credentials issued by this authority. Identities were issued project membership credentials, and these cryptographically verifiable credentials were then combined with attribute based access control policies to setup a mutually authenticated and authorized end-to-end secure channel. Your applications can make granular access control decisions at every request because they can be certain about the source and integrity of all data and instructions. You place zero implicit trust in network boundaries and intermediaries to build applications that have end-to-end application layer trust for all data in motion. ### Powerful protocols, made simple Underlying all of this is a variety of cryptographic and messaging protocols. We’ve made these protocols safe and easy to use in any application. No more having to think about creating unique cryptographic keys and issuing credentials to all application entities. No more designing ways to safely store secrets in hardware and securely distribute roots of trust. Ockam’s integrated approach takes away this complexity and gives you simple tools for: <ins>End-to-end data authenticity, integrity, and privacy in any communication topology</ins> * Create end-to-end encrypted, authenticated secure channels over any transport topology. * Create secure channels over multi-hop, multi-protocol routes - TCP, UDP, WebSockets, BLE, etc. * Provision encrypted relays for applications distributed across many edge and cloud private networks. * Make legacy protocols secure by tunneling them through mutually authenticated and encrypted portals. * Bring end-to-end encryption to enterprise messaging, pub/sub and event streams - Kafka, RabbitMQ etc. <ins>Identity-based, policy driven, application layer trust – granular authentication and authorization</ins> * Generate cryptographically provable unique identities. * Store private keys in safe vaults - hardware secure enclaves and cloud key management systems. * Operate scalable credential authorities to issue lightweight, short-lived, attribute-based credentials. * Onboard fleets of self-sovereign application identities using secure enrollment protocols. * Rotate and revoke keys and credentials – at scale, across fleets. * Define and enforce project-wide attribute based access control policies - ABAC, RBAC or ACLs. * Integrate with enterprise identity providers and policy providers for seamless employee access. ## Deep Dives Next let's dive into a step-by-step guide on our command line and programming libraries. * [__Ockam Command__](https://docs.ockam.io/reference/command) Command line tools to build and orchestrate highly secure distributed applications. Orchestrate nodes, vaults, identities, credentials, secure channels, relays, portals and more. [👉](https://docs.ockam.io/reference/command) * [__Ockam Programming Libraries__](https://docs.ockam.io/reference/libraries) Rust and Elixir libraries to build secure by design applications for any environment – from highly scalable cloud infrastructure to tiny battery operated microcontroller devices. [👉](https://docs.ockam.io/reference/libraries) * [__Ockam Protocols__](https://docs.ockam.io/reference/protocols) Cryptographic and Messaging Protocols that make up the core of Ockam and provide the foundation for end-to-end application layer trust in data. [👉](https://docs.ockam.io/reference/libraries) ## License The code in this repository is licensed under the terms of the [Apache License 2.0](LICENSE). ## Sponsorship Matching Program Ockam sponsors open source builders who are making it possible for software to be more private and secure-by-design. This includes builders of tools and libraries that Ockam depends on. Under our matching program, if you sponsor the Ockam Open Source project, we will match your contribution and pass it along to other open source developers. For example: If you sponsor Ockam for $10 a month, we will match your $10, and will send $20 back out into the community. Learn more about our [sponsorship matching program](https://github.com/sponsors/build-trust) [👉](https://github.com/sponsors/build-trust) ## Learn more about Ockam - [ockam.io](https://www.ockam.io/) - [Documentation](https://docs.ockam.io/) - [Contribute to Ockam](https://github.com/build-trust/.github/blob/main/CONTRIBUTING.md#contributing-to-ockam-on-github) - [Build Trust community Discord server](https://discord.gg/RAbjRr3kds) - [Ockam Orchestrator on AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-wsd42efzcpsxk) ", Assign "at most 3 tags" to the expected json: {"id":"2600","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"