Search Results

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 8.883635

Auditing

Auditing Cloud CMS provides a built-in audit system that track interactions between users and content objects within your content repository. The audit system produces an audit trail consisting of audit records that document the interaction between a particular user, a content object and a service. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Enabling Auditing To enable audit records, the tenant for

Score: 7.4087944

Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may

Score: 6.4037924

Audit

Audit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration This feature does need configuration. Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }

Score: 6.377604

Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object fal

Score: 6.069399

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" quyery operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud C

Score: 5.633023

Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS,

Score: 3.0243893

API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties

Score: 2.8365724

Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This port

Score: 2.7992797

Overview

Overview Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team

Score: 2.6118166