Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
note
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
Define the operating scope
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
Identity and product authorization
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
Ownership and boundaries
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
Evidence and validation
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
- Locate the Independent operating evidence not published section.
- Independent operating evidence not published
- Read and accept the Business Associate Agreement (BAA).
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Retention and privacy
important
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
note
Release requirements
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
- Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
- Breach: Unauthorized access, use, or disclosure of PHI.
- Security Rule: Safeguards to protect electronic PHI.
- Privacy Rule: Rules governing how PHI is used and disclosed.
Define the operating scope
-
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
- Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
-
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Administrative: Policies and training to ensure compliance.
- Physical: Secure access controls to data storage areas.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
-
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
- We report any security breach to you promptly, and no later than five business days after we become aware of it. See Security incidents.
-
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- We provide transparency by listing our subcontractors at Independent operating evidence not published.
-
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
- A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
-
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
- Customers can request access to audit logs by raising a Support request.
- A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
Identity and product authorization
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Ownership and boundaries
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
Evidence and validation
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
- Vinexelprotect Console and API audit logs: Captures user actions in the Vinexelprotect Console and via the Vinexelprotect API.
- data audit logs: Logged using the pgAudit extension (
pgaudit) for data.
A useful workflow makes the owner, authorization, evidence and validation visible. Illustrative product principle; no customer endorsement is claimed.
Retention and privacy
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Project management: creating, deleting, listing projects
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
connection_uripassword GETAgree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.- A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
PATCHPUTPOSTDELETE
Vinexelprotect console and API audit log example
Record an owner, project, environment, data classification and approved destinations before collecting evidence.List project branches
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
# Planning example — no product CLI has been released
asset: application-example
owner: workload-owner
environment: staging
action: review-onlyAgree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
| Field position | Example value | Description |
|---|---|---|
| 1 | fb7c2e2f-cb09-4405-b543-dbe1b88614b6 | Unique ID for the raw log event |
| 2 | 2025-05-25 10:18:45.340 +0000 | Timestamp when Airbyte extracted the record |
| 3 | { "changes": [], "sync_id": 57949 } | Metadata from the ingestion tool |
| 4 | e640c32c-0387-4fc2-8ca5-f823f7ebc4b6 | Unique identifier for the API event |
| 5 | GET | HTTP method used in the request |
| 6 | {} | Request body payload (if present) |
| 7 | Reserved for future metadata fields (empty in this case) | |
| 8 | /projects/misty-breeze-49601234/recovery plans | URL path of the API call |
| 9 | a92b3088-7f92-4871-bf91-0aac64edc4b6 | Internal ID for the response object |
| 10 | b8c58a4b-0a33-4d54-987e-4155e95a64b6 | Internal ID representing the auth/session context |
| 11 | 2025-05-24 15:42:39.088 +0000 | Actual time when the API call was made |
| 12 | misty-breeze-49601234 | Project identifier targeted by the API call |
| 13 | keycloak | Access controls mechanism used |
| 14 | 200 | HTTP status code of the response |
| 15 | {} | Resource identifiers returned (if any) |
| 16 | ListProjectBranches | Operation name associated with the endpoint |
| 17 | 0 | Internal sync batch identifier |
Release requirements
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
| Setting | Value | Description |
|---|---|---|
pgaudit.log | all, -misc | Logs all classes of SQL statements except low-risk miscellaneous commands. |
pgaudit.log_parameter | off | Parameters passed to SQL statements are not logged to avoid capturing sensitive values. |
pgaudit.log_catalog | off | Queries on system catalog tables (for example, pg_catalog) are excluded from logs to reduce noise. |
pgaudit.log_statement | on | The full SQL statement text is included in the log. |
pgaudit.log_relation | off | Only a single log entry is generated per statement, not per table or view. |
pgaudit.log_statement_once | off | SQL statements are logged with every entry, not just once per session. |
What doespgaudit.log = 'all, -misc'include?
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.misc
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
SELECTCOPY - Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
INSERTUPDATEDELETETRUNCATECOPY - FUNCTION: Function calls and
DOblocks. - Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
GRANTREVOKECREATE ROLEALTER ROLEDROP ROLE - Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
CREATE TABLEALTER INDEXDROP VIEWROLE - A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
SETSET ROLE
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
DISCARDFETCHCHECKPOINTVACUUMSET
note
Record an owner, project, environment, data classification and approved destinations before collecting evidence.CREATE ROLE ... LOGIN PASSWORDpgaudit
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
Audit log storage and forwarding
- Logs are written using the standard application data logging facility.
- Record an owner, project, environment, data classification and approved destinations before collecting evidence.
- Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
endpoint_idproject_idconnector_not_released
data audit log example
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.CREATE SCHEMA IF NOT EXISTS healthcare
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.CREATE SCHEMA IF NOT EXISTS healthcare;
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
# Policy design example — not an executable API
authorization: required
connector: not-released
approval: explicit
evidence: validation-requiredKeep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
| Field position | Example value | Description |
|---|---|---|
| 1 | 2025-05-05 20:23:01.277 | Timestamp when the log was received by the logging system. |
| 2 | <134> | Syslog priority code (facility + severity). |
| 3 | May 6 00:23:01 | Syslog timestamp (when the message was generated on the source host). |
| 4 | vm-compute-shy-waterfall-w2cn1o3t-b6vmn | Hostname or compute instance where the event occurred. |
| 5 | young-recipe-29421150/ep-calm-da | Project and endpoint name in the format <project>/<endpoint>. |
| 6 | 2025-05-06 00:23:01.277 GMT | Timestamp of the dataset event in UTC. |
| 7 | example_owner | Dataset role (user) that executed the statement. |
| 8 | example_dataset | Dataset name. |
| 9 | 1405 | Process ID (PID) of the application data backend. |
| 10 | 10.6.42.155:13702 | Client IP address and port that issued the query. |
| 11 | 68195665.57d | application data virtual transaction ID. |
| 12 | 1 | Backend process number. |
| 13 | CREATE SCHEMA | Command tag. |
| 14 | 2025-05-06 00:23:01 GMT | Statement start timestamp. |
| 15 | 16/2 | Log sequence number (LSN). |
| 16 | 767 | Statement duration in milliseconds. |
| 17 | 00000 | SQLSTATE error code (00000 = success). |
| 18 | SESSION | Log message level. |
| 19 | 1 | Session ID. |
| 20 | 1 | Subsession or transaction ID. |
| 21 | DDL | Statement type: Data Definition Language. |
| 22 | CREATE SCHEMA | Statement tag/type. |
| 23–26 | (empty) | Reserved/unused fields. |
| 27 | CREATE SCHEMA IF NOT EXISTS healthcare | Full SQL text of the statement. |
| 28 | <not logged> | Parameter values (redacted or disabled by settings like pgaudit.log_parameter). |
| 29–35 | (empty) | Reserved/unused fields. |
| 36 | review-only-example | Application name or source of the query (for example, SQL Editor in the Vinexelprotect Console). |
Extension configuration
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.pgaudit
Define the operating scope
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
- Data APIIndependent operating evidence not published
Identity and product authorization
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
- Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
- Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
Ownership and boundaries
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Evidence and validation
Keep policy revision, observation source, time and measured outcome together. Treat inferred results as unverified until tested.
important
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.
Retention and privacy
Plan protection policies, recovery validation and continuity workflows in one product. This is a frontend preview; backup, restore and replication engines are not released.
Release requirements
Define the operating scope
Start with the project account forms and IAM Central. Product permissions, connector scope and approvals must separately authorize sensitive actions.
Identity and product authorization
Record an owner, project, environment, data classification and approved destinations before collecting evidence.
Evidence and validation
Agree what is collected, where it is processed, who can access it and when it is deleted. A future connector needs its own disclosure and retention policy.
A production connector requires isolation, durable audit, idempotent operations, failure recovery, monitoring and representative validation. Existing account pages do not establish these guarantees.








