Versions Compared

Old Version 4

changes.mady.by.user David Doret

Saved on

compared with

New Version Current

changes.mady.by.user David Doret

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a sample page used to provide guidelines on how product pages should be documented. The purple note panels describe the content elements on the page.

...

The title of a product page should be composed of the short company name followed by the product name and suffixed with “ (Product)”.

The table below is contained in a page properties macro. The table must be structured with 2 columns, one header column containing property names and one standard column containing property values. The page properties macro makes it possible to build dynamic lists on other wiki pages in table format. For more information on this macro, please refer to the official documentation.

Page Properties

Vendor

Name

[Sample] Fake Acme Kafkaesque Enterprise (Fake)

The

(Vendor)

A link to the corresponding Open-Measure vendor wiki page.

Product Name

Fake Masquerading Solution

The full name of the company. Show the acronym in parenthesis if any.product.

Version

1.0

A version number for the page. Confluence keeps track of all page versions but the idea of this version number maintained manually is to inform readers of page version changes. The minor version number should be incremented whenever minor changes are applied to the page. The major version number should be incremented whenever significant changes are applied to the page.

Web Site

Product Page

https://www.open-measure.org/wiki

The main official website URL of the official home page of the company. Complementary links may be provided below.product.

Description

This is a fake company used for documentation purposesshort description of the product.

https://www.open-measure.org/miscellaneous/statuteswiki, accessed 30 mar 2020

A short description for the company, usually of the product. Usually an excerpt of the company’s about us page.

LinkedIn

https://www.linkedin.com/company/open-measure/

The URL of the LinkedIn

Twitter

https://twitter.com/open_measure

The URL of the Twitter page

…

You may then add any number of blog, social network and complementary link

IAM

✔✘

If the company sells products in the given market segment, copy paste a green check (it is a Unicode character with green color applied to it). If the company does not sell products in the given market segment, copy paste a red cross (it is a Unicode character with red color applied to it).

Workforce IAM

3rd Party IAM

Customer IAM

IoT IAM

PAM / TAM

Vendor

Axiomatics (Vendor)

Product Name

Axiomatics Policy Server

Version

1.0

Product Page

https://www.axiomatics.com/product/dynamic-authorization-applications/

Description

The fastest, most accurate and most comprehensive dynamic and externalized authorization solution available.

Axiomatics Policy Server is best-in-class software for enterprise-wide externalized dynamic authorization, delivered with Attribute Based Access Control (ABAC). Whether your pain is role explosion, toxic combinations or managing segregation of duties, this fine-grained data access control can solve your toughest challenges. You’ll be able to address complex control and compliance needs, and to more efficiently and effectively manage access to critical assets. For legacy controls, it’s a better way to manage legacy entitlements and provisioning. With dynamic authorization, you’ll get proven results:

Show ROI on investment quickly
Expand the possibilities and performance of development teams
Gain competitive advantage and speed-to-market
Unmatched scalability and performance makes Axiomatics Policy Server the preferred choice for implementing Attribute Based Access Control in many global enterprises and government agencies.

https://www.axiomatics.com/product/dynamic-authorization-applications/, accessed 29 mar 2020

Authorization Server

✔

Access Control Policy Management

✔

Deployment

Cloud, On-premises, Hybrid

Access Control Policy Workflows

✔

Multiple Authorization Domains Management

✔

ABAC

✔

XACML 3.0

✔

SDK

✔

API

✔

Micro-Services

✔

vendor’s product web page, providing source URL and access date.

Feature / characteristic 1

Then, list the product features and characteristics row by row

✔✘

Add a green check if the characteristic or feature is implemented in the product and a red cross if it isn’t. Please note that we are working on a more sophisticated scale, you may preview it here Feature Support Scale and try to use it already. But it requires that standardized definitions for product features and characteristics be produced first, thus we may leave this for future enhancement at this current point in time.

Feature / characteristic 2

…

Feature / characteristic 3

…

…

…

For page labels, we use lower-case words with dashes. Add at least the vendorproduct-record label that makes it possible to easily retrieve the list of all vendor product pages. Add also a label with the company name and another one for the product name. Finally, add any number of complementary labels that may prove useful to retrieve that companyproduct, but do not exaggerate as too many labels is counter-productive for research purposes.