https://docs.protegrity.com/dsg/3.3.0.1/docs/dsg_tech_arch/Recent content in Technical Architecture onHugoenhttps://docs.protegrity.com/dsg/3.3.0.1/docs/dsg_tech_arch/dsg_cop_architecture/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/dsg/3.3.0.1/docs/dsg_tech_arch/dsg_cop_architecture/<h2 id="cop-overview">CoP overview</h2> <p>CoP is a key paradigm used in the Protegrity Gateway Technology. The CoP technology enables a CoP administrator to create a set of rules that instructs the gateway on how to process data that traverses it.</p> <p>The CoP technology is also a key component from a user experience perspective. The hierarchical structure of the rules is just as important as the rules themselves. The set of rules, their structure, and an easy-to-use interface results in a powerful toolset called the CoP.</p>https://docs.protegrity.com/dsg/3.3.0.1/docs/dsg_tech_arch/dsg_dynamic_cop/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/dsg/3.3.0.1/docs/dsg_tech_arch/dsg_dynamic_cop/<p>Ruleset execution can be segregated into Static CoP and Dynamic CoP. When the payload type and structure are predictable and known at system configuration time, you can define Rulesets for such payloads and process the data using Static CoP. It is assumed in Static CoP that a user who defines Rulesets is authorized and holds permission to access DSG nodes.</p> <p>When organizations are divided into disparate systems or applications, and each system user needs to send custom payloads on the fly to DSG nodes with minimal predictability, granting users access to DSG nodes to define Rulesets becomes risky. In such situations, you can use Dynamic CoP to send extraction and transformation rules in the request header, along with the data to be protected in the request message body.</p>