Configure a PostgreSQL/Pivotal Greenplum Database check
Configure a PostgreSQL/Pivotal Greenplum Database control to execute custom SQL statements on PostgreSQL/Pivotal Greenplum databases and create corresponding policy reports.
Identify this control
The statement you provide is like the control name that describes what it is and how it should be implemented in the environment. You need to decide which category and sub-category the control belongs to. This is important because users can search and filter controls by category, they can also search by keywords in the statement.
Control Technologies
Your control may apply to many technologies. In case the values for each technology are different, then select each technology you are interested in individually and provide a rationale, statement, and description for this control.
If you plan to use the same values for many technologies you only need to specify them once. Define your values in the "Default Values for Control Technologies" section first and then select the check box for each technology you want or click the Apply to All Technologies . you can view that the values get copied automatically to each technology that you select.
Rationale
Enter a rationale statement describing how the control should be implemented for each technology.
SQL Statement
Enter your SQL statement here. This value can have a maximum of 32000 characters. Only SELECT Statements are supported for this check.
Make sure you only use supported output data types when forming SQL statements. If you use an unsupported data type in the SQL statement, then the control posture will result in Error. To avoid this, use the supported data types only.
Supported data types:
smallint, integer, bigint, smallserial, bigserial, serial, real, double precision, numeric, char, varchar, Boolean, money, bit, XML, date, time, timestamp, cidradr, macaddr, json, UUID, bytea
Description
Describe your SQL statement here and it will appear in compliance policies and reports. You can also add your SQL statement to the description if you wish to view it in policies and reports.
Remediation
Add remediation steps for this check.
Reporting Options
Your compliance reports and PA dashboard display the compliance status (Passed, Failed, or Error) for each control instance. The status Error is returned in cases where errors occurred during control evaluation. This means the control was not tested for compliance.
If you do not want to see the Error status then you can ignore these errors and set their status to Pass or Fail. This reflects in your reports accordingly.
References
Add up to 10 references for the control. These may be references to internal policies, documents and web sites. For each reference, enter a description, a URL, or both. You must start a URL with http://, https:// or ftp://. For example, enter http://www.qualys.com to link to the Qualys website. Once added, users have the option to include references in policy reports.
Good to Know
By default, up to 256 rows are returned. You can edit this limit in the compliance option profile. The maximum limit that you can set is 5000 rows.