DataSafeClient

class oci.data_safe.DataSafeClient(config, **kwargs)

APIs for using Oracle Data Safe.

Methods

__init__(config, **kwargs) Creates a new service client
activate_target_database(…) Reactivates a previously deactivated Data Safe target database.
change_data_safe_private_endpoint_compartment(…) Moves the Data Safe private endpoint and its dependent resources to the specified compartment.
change_on_prem_connector_compartment(…) Moves the specified on-premises connector into a different compartment.
change_security_assessment_compartment(…) Moves the specified saved security assessment or future scheduled assessments into a different compartment.
change_target_database_compartment(…) Moves the Data Safe target database to the specified compartment.
change_user_assessment_compartment(…) Moves the specified saved user assessment or future scheduled assessments into a different compartment.
compare_security_assessment(…) Compares two security assessments.
compare_user_assessment(user_assessment_id, …) Compares two user assessments.
create_data_safe_private_endpoint(…) Creates a new Data Safe private endpoint.
create_on_prem_connector(…) Creates a new on-premises connector.
create_security_assessment(…) Creates a new saved security assessment for one or multiple targets in a compartment.
create_target_database(…) Registers the specified database with Data Safe and creates a Data Safe target database in the Data Safe Console.
create_user_assessment(…) Creates a new saved user assessment for one or multiple targets in a compartment.
deactivate_target_database(…) Deactivates a target database in Data Safe.
delete_data_safe_private_endpoint(…) Deletes the specified Data Safe private endpoint.
delete_on_prem_connector(…) Deletes the specified on-premises connector.
delete_security_assessment(…) Deletes the specified saved security assessment or schedule.
delete_target_database(target_database_id, …) Deregisters the specified database from Data Safe and removes the target database from the Data Safe Console.
delete_user_assessment(user_assessment_id, …) Deletes the specified saved user assessment or schedule.
download_privilege_script(**kwargs) Downloads the privilege script to grant/revoke required roles from the Data Safe account on the target database.
download_security_assessment_report(…) Downloads the report of the specified security assessment.
download_user_assessment_report(…) Downloads the report of the specified user assessment.
enable_data_safe_configuration(…) Enables Data Safe in the tenancy and region.
generate_on_prem_connector_configuration(…) Creates and downloads the configuration of the specified on-premises connector.
generate_security_assessment_report(…) Generates the report of the specified security assessment.
generate_user_assessment_report(…) Generates the report of the specified user assessment.
get_data_safe_configuration(**kwargs) Gets the details of the Data Safe configuration.
get_data_safe_private_endpoint(…) Gets the details of the specified Data Safe private endpoint.
get_on_prem_connector(on_prem_connector_id, …) Gets the details of the specified on-premises connector.
get_security_assessment(…) Gets the details of the specified security assessment.
get_security_assessment_comparison(…) Gets the details of the comparison report on the security assessments submitted for comparison.
get_target_database(target_database_id, **kwargs) Returns the details of the specified Data Safe target database.
get_user_assessment(user_assessment_id, **kwargs) Gets a user assessment by identifier.
get_user_assessment_comparison(…) Gets the details of the comparison report for the user assessments provided.
get_work_request(work_request_id, **kwargs) Gets the details of the specified work request.
list_data_safe_private_endpoints(…) Gets a list of Data Safe private endpoints.
list_findings(security_assessment_id, **kwargs) List all the findings from all the targets in the specified assessment.
list_grants(user_assessment_id, user_key, …) Gets a list of grants for a particular user in the specified user assessment.
list_on_prem_connectors(compartment_id, **kwargs) Gets a list of on-premises connectors.
list_security_assessments(compartment_id, …) Gets a list of security assessments.
list_target_databases(compartment_id, **kwargs) Returns the list of registered target databases in Data Safe.
list_user_analytics(user_assessment_id, **kwargs) Gets a list of aggregated user details from the specified user assessment.
list_user_assessments(compartment_id, **kwargs) Gets a list of user assessments.
list_users(user_assessment_id, **kwargs) Gets a list of users of the specified user assessment.
list_work_request_errors(work_request_id, …) Gets a list of errors for the specified work request.
list_work_request_logs(work_request_id, **kwargs) Gets a list of log entries for the specified work request.
list_work_requests(compartment_id, **kwargs) Gets a list of work requests.
refresh_security_assessment(…) Runs a security assessment, refreshes the latest assessment, and saves it for future reference.
refresh_user_assessment(user_assessment_id, …) Refreshes the latest assessment and saves it for future reference.
set_security_assessment_baseline(…) Sets the saved security assessment as the baseline in the compartment where the the specified assessment resides.
set_user_assessment_baseline(…) Sets the saved user assessment as the baseline in the compartment where the specified assessment resides.
unset_security_assessment_baseline(…) Removes the baseline setting for the saved security assessment.
unset_user_assessment_baseline(…) Removes the baseline setting for the saved user assessment.
update_data_safe_private_endpoint(…) Updates one or more attributes of the specified Data Safe private endpoint.
update_on_prem_connector(…) Updates one or more attributes of the specified on-premises connector.
update_on_prem_connector_wallet(…) Updates the wallet for the specified on-premises connector to a new version.
update_security_assessment(…) Updates one or more attributes of the specified security assessment.
update_target_database(target_database_id, …) Updates one or more attributes of the specified Data Safe target database.
update_user_assessment(user_assessment_id, …) Updates one or more attributes of the specified user assessment.
__init__(config, **kwargs)

Creates a new service client

Parameters:
  • config (dict) – Configuration keys and values as per SDK and Tool Configuration. The from_file() method can be used to load configuration from a file. Alternatively, a dict can be passed. You can validate_config the dict using validate_config()
  • service_endpoint (str) – (optional) The endpoint of the service to call using this client. For example https://iaas.us-ashburn-1.oraclecloud.com. If this keyword argument is not provided then it will be derived using the region in the config parameter. You should only provide this keyword argument if you have an explicit need to specify a service endpoint.
  • timeout (float or tuple(float, float)) – (optional) The connection and read timeouts for the client. The default values are connection timeout 10 seconds and read timeout 60 seconds. This keyword argument can be provided as a single float, in which case the value provided is used for both the read and connection timeouts, or as a tuple of two floats. If a tuple is provided then the first value is used as the connection timeout and the second value as the read timeout.
  • signer (AbstractBaseSigner) –

    (optional) The signer to use when signing requests made by the service client. The default is to use a Signer based on the values provided in the config parameter.

    One use case for this parameter is for Instance Principals authentication by passing an instance of InstancePrincipalsSecurityTokenSigner as the value for this keyword argument

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to all calls made by this service client (i.e. at the client level). There is no retry strategy applied by default. Retry strategies can also be applied at the operation level by passing a retry_strategy keyword argument as part of calling the operation. Any value provided at the operation level will override whatever is specified at the client level.

    This should be one of the strategies available in the retry module. A convenience DEFAULT_RETRY_STRATEGY is also available. The specifics of the default retry strategy are described here.

  • circuit_breaker_strategy (obj) – (optional) A circuit breaker strategy to apply to all calls made by this service client (i.e. at the client level). This client uses DEFAULT_CIRCUIT_BREAKER_STRATEGY as default if no circuit breaker strategy is provided. The specifics of circuit breaker strategy are described here.
  • circuit_breaker_callback (function) – (optional) Callback function to receive any exceptions triggerred by the circuit breaker.
activate_target_database(activate_target_database_details, target_database_id, **kwargs)

Reactivates a previously deactivated Data Safe target database.

Parameters:
  • activate_target_database_details (oci.data_safe.models.ActivateTargetDatabaseDetails) – (required) The details used to reactivate a target database in Data Safe.
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use activate_target_database API.

change_data_safe_private_endpoint_compartment(data_safe_private_endpoint_id, change_data_safe_private_endpoint_compartment_details, **kwargs)

Moves the Data Safe private endpoint and its dependent resources to the specified compartment.

Parameters:
  • data_safe_private_endpoint_id (str) – (required) The OCID of the private endpoint.
  • change_data_safe_private_endpoint_compartment_details (oci.data_safe.models.ChangeDataSafePrivateEndpointCompartmentDetails) – (required) The details used to change the compartment of a Data Safe private endpoint.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use change_data_safe_private_endpoint_compartment API.

change_on_prem_connector_compartment(on_prem_connector_id, change_on_prem_connector_compartment_details, **kwargs)

Moves the specified on-premises connector into a different compartment.

Parameters:
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • change_on_prem_connector_compartment_details (oci.data_safe.models.ChangeOnPremConnectorCompartmentDetails) – (required) The details used to change the compartment of an on-premises connector.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use change_on_prem_connector_compartment API.

change_security_assessment_compartment(security_assessment_id, change_security_assessment_compartment_details, **kwargs)

Moves the specified saved security assessment or future scheduled assessments into a different compartment.

To start, call first the operation ListSecurityAssessments with filters “type = save_schedule”. This returns the scheduleAssessmentId. Then, call this changeCompartment with the scheduleAssessmentId.

The existing saved security assessments created due to the schedule are not moved. However, all new saves will be associated with the new compartment.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • change_security_assessment_compartment_details (oci.data_safe.models.ChangeSecurityAssessmentCompartmentDetails) – (required) The details used to change the compartment of a security assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use change_security_assessment_compartment API.

change_target_database_compartment(target_database_id, change_target_database_compartment_details, **kwargs)

Moves the Data Safe target database to the specified compartment.

Parameters:
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • change_target_database_compartment_details (oci.data_safe.models.ChangeTargetDatabaseCompartmentDetails) – (required) Details of the move compartment request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use change_target_database_compartment API.

change_user_assessment_compartment(user_assessment_id, change_user_assessment_compartment_details, **kwargs)

Moves the specified saved user assessment or future scheduled assessments into a different compartment. To start storing scheduled user assessments on a different compartment, first call the operation ListUserAssessments with the filters “type = save_schedule”. That call returns the scheduleAssessmentId. Then call ChangeUserAssessmentCompartment with the scheduleAssessmentId. The existing saved user assessments created per the schedule are not be moved. However, all new saves will be associated with the new compartment.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • change_user_assessment_compartment_details (oci.data_safe.models.ChangeUserAssessmentCompartmentDetails) – (required) The details used to change the compartment of a user assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use change_user_assessment_compartment API.

compare_security_assessment(security_assessment_id, compare_security_assessment_details, **kwargs)

Compares two security assessments. For this comparison, a security assessment can be a saved assessment, a latest assessment, or a baseline assessment. For example, you can compare saved assessment or a latest assessment against a baseline.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • compare_security_assessment_details (oci.data_safe.models.CompareSecurityAssessmentDetails) – (required) Details of the security assessment comparison.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use compare_security_assessment API.

compare_user_assessment(user_assessment_id, compare_user_assessment_details, **kwargs)

Compares two user assessments. For this comparison, a user assessment can be a saved, a latest assessment, or a baseline. As an example, it can be used to compare a user assessment saved or a latest assessment with a baseline.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • compare_user_assessment_details (oci.data_safe.models.CompareUserAssessmentDetails) – (required) Details of the user assessment comparison.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use compare_user_assessment API.

create_data_safe_private_endpoint(create_data_safe_private_endpoint_details, **kwargs)

Creates a new Data Safe private endpoint.

Parameters:
  • create_data_safe_private_endpoint_details (oci.data_safe.models.CreateDataSafePrivateEndpointDetails) – (required) Details to create a new private endpoint.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type DataSafePrivateEndpoint

Return type:

Response

Example:

Click here to see an example of how to use create_data_safe_private_endpoint API.

create_on_prem_connector(create_on_prem_connector_details, **kwargs)

Creates a new on-premises connector.

Parameters:
  • create_on_prem_connector_details (oci.data_safe.models.CreateOnPremConnectorDetails) – (required) The details used to create a new on-premises connector.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type OnPremConnector

Return type:

Response

Example:

Click here to see an example of how to use create_on_prem_connector API.

create_security_assessment(create_security_assessment_details, **kwargs)

Creates a new saved security assessment for one or multiple targets in a compartment. When this operation is performed, it will save the latest assessments in the specified compartment. If a schedule is passed, it will persist the latest assessments, at the defined date and time, in the format defined by RFC3339.

Parameters:
  • create_security_assessment_details (oci.data_safe.models.CreateSecurityAssessmentDetails) – (required) The details used to create a new saved security assessment.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type SecurityAssessment

Return type:

Response

Example:

Click here to see an example of how to use create_security_assessment API.

create_target_database(create_target_database_details, **kwargs)

Registers the specified database with Data Safe and creates a Data Safe target database in the Data Safe Console.

Parameters:
  • create_target_database_details (oci.data_safe.models.CreateTargetDatabaseDetails) – (required) Details of the target database.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type TargetDatabase

Return type:

Response

Example:

Click here to see an example of how to use create_target_database API.

create_user_assessment(create_user_assessment_details, **kwargs)

Creates a new saved user assessment for one or multiple targets in a compartment. It saves the latest assessments in the specified compartment. If a scheduled is passed in, this operation persists the latest assessments that exist at the defined date and time, in the format defined by RFC3339.

Parameters:
  • create_user_assessment_details (oci.data_safe.models.CreateUserAssessmentDetails) – (required) The details used to create a new saved user assessment.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type UserAssessment

Return type:

Response

Example:

Click here to see an example of how to use create_user_assessment API.

deactivate_target_database(target_database_id, **kwargs)

Deactivates a target database in Data Safe.

Parameters:
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use deactivate_target_database API.

delete_data_safe_private_endpoint(data_safe_private_endpoint_id, **kwargs)

Deletes the specified Data Safe private endpoint.

Parameters:
  • data_safe_private_endpoint_id (str) – (required) The OCID of the private endpoint.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_data_safe_private_endpoint API.

delete_on_prem_connector(on_prem_connector_id, **kwargs)

Deletes the specified on-premises connector.

Parameters:
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_on_prem_connector API.

delete_security_assessment(security_assessment_id, **kwargs)

Deletes the specified saved security assessment or schedule. To delete a security assessment schedule, first call the operation ListSecurityAssessments with filters “type = save_schedule”. That operation returns the scheduleAssessmentId. Then, call DeleteSecurityAssessment with the scheduleAssessmentId. If the assessment being deleted is the baseline for that compartment, then it will impact all baselines in the compartment.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_security_assessment API.

delete_target_database(target_database_id, **kwargs)

Deregisters the specified database from Data Safe and removes the target database from the Data Safe Console.

Parameters:
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_target_database API.

delete_user_assessment(user_assessment_id, **kwargs)

Deletes the specified saved user assessment or schedule. To delete a user assessment schedule, first call the operation ListUserAssessments with filters “type = save_schedule”. That call returns the scheduleAssessmentId. Then call DeleteUserAssessment with the scheduleAssessmentId. If the assessment being deleted is the baseline for that compartment, then it will impact all baselines in the compartment.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_user_assessment API.

download_privilege_script(**kwargs)

Downloads the privilege script to grant/revoke required roles from the Data Safe account on the target database.

Parameters:
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type stream

Return type:

Response

Example:

Click here to see an example of how to use download_privilege_script API.

download_security_assessment_report(security_assessment_id, download_security_assessment_report_details, **kwargs)

Downloads the report of the specified security assessment. To download the security assessment report, it needs to be generated first. Please use GenerateSecurityAssessmentReport to generate a downloadable report in the preferred format (PDF, XLS).

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • download_security_assessment_report_details (oci.data_safe.models.DownloadSecurityAssessmentReportDetails) – (required) Details of the report.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type stream

Return type:

Response

Example:

Click here to see an example of how to use download_security_assessment_report API.

download_user_assessment_report(user_assessment_id, download_user_assessment_report_details, **kwargs)

Downloads the report of the specified user assessment. To download the user assessment report, it needs to be generated first. Please use GenerateUserAssessmentReport to generate a downloadable report in the preferred format (PDF, XLS).

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • download_user_assessment_report_details (oci.data_safe.models.DownloadUserAssessmentReportDetails) – (required) Details of the report.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type stream

Return type:

Response

Example:

Click here to see an example of how to use download_user_assessment_report API.

enable_data_safe_configuration(enable_data_safe_configuration_details, **kwargs)

Enables Data Safe in the tenancy and region.

Parameters:
  • enable_data_safe_configuration_details (oci.data_safe.models.EnableDataSafeConfigurationDetails) – (required) The details used to enable Data Safe.
  • compartment_id (str) – (optional) A filter to return only resources that match the specified compartment OCID.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use enable_data_safe_configuration API.

generate_on_prem_connector_configuration(generate_on_prem_connector_configuration_details, on_prem_connector_id, **kwargs)

Creates and downloads the configuration of the specified on-premises connector.

Parameters:
  • generate_on_prem_connector_configuration_details (oci.data_safe.models.GenerateOnPremConnectorConfigurationDetails) – (required) The details used to create and download on-premises connector’s configuration.
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type stream

Return type:

Response

Example:

Click here to see an example of how to use generate_on_prem_connector_configuration API.

generate_security_assessment_report(security_assessment_id, generate_security_assessment_report_details, **kwargs)

Generates the report of the specified security assessment. You can get the report in PDF or XLS format. After generating the report, use DownloadSecurityAssessmentReport to download it in the preferred format.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • generate_security_assessment_report_details (oci.data_safe.models.GenerateSecurityAssessmentReportDetails) – (required) Details of the report.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use generate_security_assessment_report API.

generate_user_assessment_report(user_assessment_id, generate_user_assessment_report_details, **kwargs)

Generates the report of the specified user assessment. The report is available in PDF or XLS format. After generating the report, use DownloadUserAssessmentReport to download it in the preferred format.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • generate_user_assessment_report_details (oci.data_safe.models.GenerateUserAssessmentReportDetails) – (required) Details of the report.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use generate_user_assessment_report API.

get_data_safe_configuration(**kwargs)

Gets the details of the Data Safe configuration.

Parameters:
  • compartment_id (str) – (optional) A filter to return only resources that match the specified compartment OCID.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type DataSafeConfiguration

Return type:

Response

Example:

Click here to see an example of how to use get_data_safe_configuration API.

get_data_safe_private_endpoint(data_safe_private_endpoint_id, **kwargs)

Gets the details of the specified Data Safe private endpoint.

Parameters:
  • data_safe_private_endpoint_id (str) – (required) The OCID of the private endpoint.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type DataSafePrivateEndpoint

Return type:

Response

Example:

Click here to see an example of how to use get_data_safe_private_endpoint API.

get_on_prem_connector(on_prem_connector_id, **kwargs)

Gets the details of the specified on-premises connector.

Parameters:
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type OnPremConnector

Return type:

Response

Example:

Click here to see an example of how to use get_on_prem_connector API.

get_security_assessment(security_assessment_id, **kwargs)

Gets the details of the specified security assessment.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type SecurityAssessment

Return type:

Response

Example:

Click here to see an example of how to use get_security_assessment API.

get_security_assessment_comparison(security_assessment_id, comparison_security_assessment_id, **kwargs)

Gets the details of the comparison report on the security assessments submitted for comparison.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • comparison_security_assessment_id (str) – (required) The OCID of the baseline security assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type SecurityAssessmentComparison

Return type:

Response

Example:

Click here to see an example of how to use get_security_assessment_comparison API.

get_target_database(target_database_id, **kwargs)

Returns the details of the specified Data Safe target database.

Parameters:
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type TargetDatabase

Return type:

Response

Example:

Click here to see an example of how to use get_target_database API.

get_user_assessment(user_assessment_id, **kwargs)

Gets a user assessment by identifier.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type UserAssessment

Return type:

Response

Example:

Click here to see an example of how to use get_user_assessment API.

get_user_assessment_comparison(user_assessment_id, comparison_user_assessment_id, **kwargs)

Gets the details of the comparison report for the user assessments provided.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • comparison_user_assessment_id (str) – (required) The OCID of the baseline user assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type UserAssessmentComparison

Return type:

Response

Example:

Click here to see an example of how to use get_user_assessment_comparison API.

get_work_request(work_request_id, **kwargs)

Gets the details of the specified work request.

Parameters:
  • work_request_id (str) – (required) The OCID of the work request.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type WorkRequest

Return type:

Response

Example:

Click here to see an example of how to use get_work_request API.

list_data_safe_private_endpoints(compartment_id, **kwargs)

Gets a list of Data Safe private endpoints.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • display_name (str) – (optional) A filter to return only resources that match the specified display name.
  • vcn_id (str) – (optional) A filter to return only resources that match the specified VCN OCID.
  • lifecycle_state (str) –

    (optional) A filter to return only resources that match the specified lifecycle state.

    Allowed values are: “CREATING”, “UPDATING”, “ACTIVE”, “DELETING”, “DELETED”, “FAILED”, “NA”

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field used for sorting. Only one sorting order (sortOrder) can be specified. The default order for TIMECREATED is descending. The default order for DISPLAYNAME is ascending. The DISPLAYNAME sort order is case sensitive.

    Allowed values are: “TIMECREATED”, “DISPLAYNAME”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of DataSafePrivateEndpointSummary

Return type:

Response

Example:

Click here to see an example of how to use list_data_safe_private_endpoints API.

list_findings(security_assessment_id, **kwargs)

List all the findings from all the targets in the specified assessment.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • severity (str) –

    (optional) A filter to return only findings of a particular risk level.

    Allowed values are: “HIGH”, “MEDIUM”, “LOW”, “EVALUATE”, “ADVISORY”, “PASS”

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • finding_key (str) – (optional) Each finding has a key. This key is same for the finding across targets
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of FindingSummary

Return type:

Response

Example:

Click here to see an example of how to use list_findings API.

list_grants(user_assessment_id, user_key, **kwargs)

Gets a list of grants for a particular user in the specified user assessment. A user grant contains details such as the privilege name, type, category, and depth level. The depth level indicates how deep in the hierarchy of roles granted to roles a privilege grant is. The userKey in this operation is a system-generated identifier. Perform the operation ListUsers to get the userKey for a particular user.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • user_key (str) – (required) The unique user key. This is a system-generated identifier. ListUsers gets the user key for a user.
  • grant_key (str) – (optional) A filter to return only items that match the specified user grant key.
  • grant_name (str) – (optional) A filter to return only items that match the specified user grant name.
  • privilege_type (str) – (optional) A filter to return only items that match the specified privilege grant type.
  • privilege_category (str) – (optional) A filter to return only items that match the specified user privilege category.
  • depth_level (int) – (optional) A filter to return only items that match the specified user grant depth level.
  • depth_level_greater_than_or_equal_to (int) – (optional) A filter to return only items that are at a level greater than or equal to the specified user grant depth level.
  • depth_level_less_than (int) – (optional) A filter to return only items that are at a level less than the specified user grant depth level.
  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field to sort by. You can specify only one sort order (sortOrder). The default order for grantName is ascending.

    Allowed values are: “grantName”, “grantType”, “privilegeCategory”, “depthLevel”, “key”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of GrantSummary

Return type:

Response

Example:

Click here to see an example of how to use list_grants API.

list_on_prem_connectors(compartment_id, **kwargs)

Gets a list of on-premises connectors.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • on_prem_connector_id (str) – (optional) A filter to return only the on-premises connector that matches the specified id.
  • display_name (str) – (optional) A filter to return only resources that match the specified display name.
  • on_prem_connector_lifecycle_state (str) –

    (optional) A filter to return only on-premises connector resources that match the specified lifecycle state.

    Allowed values are: “CREATING”, “UPDATING”, “ACTIVE”, “INACTIVE”, “DELETING”, “DELETED”, “FAILED”

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field used for sorting. Only one sorting order (sortOrder) can be specified. The default order for TIMECREATED is descending. The default order for DISPLAYNAME is ascending. The DISPLAYNAME sort order is case sensitive.

    Allowed values are: “TIMECREATED”, “DISPLAYNAME”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of OnPremConnectorSummary

Return type:

Response

Example:

Click here to see an example of how to use list_on_prem_connectors API.

list_security_assessments(compartment_id, **kwargs)

Gets a list of security assessments.

The ListSecurityAssessments operation returns only the assessments in the specified compartmentId. The list does not include any subcompartments of the compartmentId passed.

The parameter accessLevel specifies whether to return only those compartments for which the requestor has INSPECT permissions on at least one resource directly or indirectly (ACCESSIBLE) (the resource can be in a subcompartment) or to return Not Authorized if Principal doesn’t have access to even one of the child compartments. This is valid only when compartmentIdInSubtree is set to true.

The parameter compartmentIdInSubtree applies when you perform ListSecurityAssessments on the compartmentId passed and when it is set to true, the entire hierarchy of compartments can be returned. To get a full list of all compartments and subcompartments in the tenancy (root compartment), set the parameter compartmentIdInSubtree to true and accessLevel to ACCESSIBLE.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • display_name (str) – (optional) A filter to return only resources that match the specified display name.
  • type (str) –

    (optional) A filter to return only items that match the specified security assessment type.

    Allowed values are: “LATEST”, “SAVED”, “SAVE_SCHEDULE”, “COMPARTMENT”

  • schedule_assessment_id (str) – (optional) The OCID of the security assessment of type SAVE_SCHEDULE.
  • is_schedule_assessment (bool) – (optional) A filter to return only security assessments of type save schedule.
  • triggered_by (str) –

    (optional) A filter to return only security asessments that were created by either user or system.

    Allowed values are: “USER”, “SYSTEM”

  • target_id (str) – (optional) A filter to return only items that match the specified target.
  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • is_baseline (bool) – (optional) A filter to return only security assessments that are set as baseline.
  • sort_by (str) –

    (optional) The field to sort by. You can specify only one sort order(sortOrder). The default order for timeCreated is descending.

    Allowed values are: “timeCreated”, “displayName”

  • time_created_greater_than_or_equal_to (datetime) –

    (optional) A filter to return only security assessments that were created after the specified date and time, as defined by RFC3339. Using TimeCreatedGreaterThanOrEqualToQueryParam parameter retrieves all assessments created after that date.

    Example: 2016-12-19T16:39:57.600Z

  • time_created_less_than (datetime) –

    (optional) Search for items that were created before a specific date. Specifying this parameter corresponding timeCreatedLessThan parameter will retrieve all items created before the specified created date, in “YYYY-MM-ddThh:mmZ” format with a Z offset, as defined by RFC 3339.

    Example: 2016-12-19T16:39:57.600Z

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • lifecycle_state (str) –

    (optional) A filter to return only resources that match the specified lifecycle state.

    Allowed values are: “CREATING”, “SUCCEEDED”, “UPDATING”, “DELETING”, “FAILED”

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of SecurityAssessmentSummary

Return type:

Response

Example:

Click here to see an example of how to use list_security_assessments API.

list_target_databases(compartment_id, **kwargs)

Returns the list of registered target databases in Data Safe.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • target_database_id (str) – (optional) A filter to return the target database that matches the specified OCID.
  • display_name (str) – (optional) A filter to return only resources that match the specified display name.
  • lifecycle_state (str) –

    (optional) A filter to return the target databases that matches the current state of the target database.

    Allowed values are: “CREATING”, “UPDATING”, “ACTIVE”, “INACTIVE”, “DELETING”, “DELETED”, “NEEDS_ATTENTION”, “FAILED”

  • database_type (str) –

    (optional) A filter to return target databases that match the database type of the target database.

    Allowed values are: “DATABASE_CLOUD_SERVICE”, “AUTONOMOUS_DATABASE”, “INSTALLED_DATABASE”

  • infrastructure_type (str) –

    (optional) A filter to return target databases that match the infrastructure type of the target database.

    Allowed values are: “ORACLE_CLOUD”, “CLOUD_AT_CUSTOMER”, “ON_PREMISES”, “NON_ORACLE_CLOUD”

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field used for sorting. Only one sorting order (sortOrder) can be specified. The default order for TIMECREATED is descending. The default order for DISPLAYNAME is ascending. The DISPLAYNAME sort order is case sensitive.

    Allowed values are: “TIMECREATED”, “DISPLAYNAME”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of TargetDatabaseSummary

Return type:

Response

Example:

Click here to see an example of how to use list_target_databases API.

list_user_analytics(user_assessment_id, **kwargs)

Gets a list of aggregated user details from the specified user assessment. This provides information about the overall state of database user security. For example, the user details include how many users have the DBA role and how many users are in the critical category. This data is especially useful content for dashboards or to support analytics.

When you perform the ListUserAnalytics operation, if the parameter compartmentIdInSubtree is set to “true,” and if the parameter accessLevel is set to ACCESSIBLE, then the operation returns compartments in which the requestor has INSPECT permissions on at least one resource, directly or indirectly (in subcompartments). If the operation is performed at the root compartment. If the requestor does not have access to at least one subcompartment of the compartment specified by compartmentId, then “Not Authorized” is returned.

The parameter compartmentIdInSubtree applies when you perform ListUserAnalytics on the compartmentId passed and when it is set to true, the entire hierarchy of compartments can be returned.

To use ListUserAnalytics to get a full list of all compartments and subcompartments in the tenancy from the root compartment, set the parameter compartmentIdInSubtree to true and accessLevel to ACCESSIBLE.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • user_category (str) – (optional) A filter to return only items that match the specified user category.
  • user_key (str) – (optional) A filter to return only items that match the specified user key.
  • account_status (str) – (optional) A filter to return only items that match the specified account status.
  • authentication_type (str) – (optional) A filter to return only items that match the specified authentication type.
  • user_name (str) – (optional) A filter to return only items that match the specified user name.
  • target_id (str) – (optional) A filter to return only items that match the specified target.
  • time_last_login_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose last login time in the database is greater than or equal to the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • time_last_login_less_than (datetime) –

    (optional) A filter to return users whose last login time in the database is less than the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_user_created_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose creation time in the database is greater than or equal to the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_user_created_less_than (datetime) –

    (optional) A filter to return users whose creation time in the database is less than the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_password_last_changed_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose last password change in the database is greater than or equal to the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • time_password_last_changed_less_than (datetime) –

    (optional) A filter to return users whose last password change in the database is less than the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field to sort by. You can specify only one sort order (sortOrder). The default order for userName is ascending.

    Allowed values are: “userName”, “userCategory”, “accountStatus”, “timeLastLogin”, “targetId”, “timeUserCreated”, “authenticationType”, “timePasswordChanged”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of UserAggregation

Return type:

Response

Example:

Click here to see an example of how to use list_user_analytics API.

list_user_assessments(compartment_id, **kwargs)

Gets a list of user assessments.

The ListUserAssessments operation returns only the assessments in the specified compartmentId. The list does not include any subcompartments of the compartmentId passed.

The parameter accessLevel specifies whether to return only those compartments for which the requestor has INSPECT permissions on at least one resource directly or indirectly (ACCESSIBLE) (the resource can be in a subcompartment) or to return Not Authorized if Principal doesn’t have access to even one of the child compartments. This is valid only when compartmentIdInSubtree is set to true.

The parameter compartmentIdInSubtree applies when you perform ListUserAssessments on the compartmentId passed and when it is set to true, the entire hierarchy of compartments can be returned. To get a full list of all compartments and subcompartments in the tenancy (root compartment), set the parameter compartmentIdInSubtree to true and accessLevel to ACCESSIBLE.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • display_name (str) – (optional) A filter to return only resources that match the specified display name.
  • schedule_user_assessment_id (str) – (optional) The OCID of the user assessment of type SAVE_SCHEDULE.
  • is_schedule_assessment (bool) – (optional) A filter to return only user assessments of type SAVE_SCHEDULE.
  • is_baseline (bool) – (optional) A filter to return only user assessments that are set as baseline.
  • target_id (str) – (optional) A filter to return only items that match the specified target.
  • type (str) –

    (optional) A filter to return only items that match the specified assessment type.

    Allowed values are: “LATEST”, “SAVED”, “COMPARTMENT”, “SAVE_SCHEDULE”

  • triggered_by (str) –

    (optional) A filter to return user assessments that were created by either the system or by a user only.

    Allowed values are: “USER”, “SYSTEM”

  • time_created_greater_than_or_equal_to (datetime) –

    (optional) A filter to return only user assessments that were created after the specified date and time, as defined by RFC3339. Using timeCreatedGreaterThanOrEqualTo parameter retrieves all assessments created after that date.

    Example: 2016-12-19T16:39:57.600Z

  • time_created_less_than (datetime) –

    (optional) Search for items that were created before a specific date. Specifying this parameter corresponding timeCreatedLessThan parameter will retrieve all items created before the specified created date, in “YYYY-MM-ddThh:mmZ” format with a Z offset, as defined by RFC 3339.

    Example: 2016-12-19T16:39:57.600Z

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • lifecycle_state (str) –

    (optional) The current state of the user assessment.

    Allowed values are: “CREATING”, “SUCCEEDED”, “UPDATING”, “DELETING”, “FAILED”

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field to sort by. You can specify only one sort order (sortOrder). The default order for timeCreated is descending.

    Allowed values are: “timeCreated”, “displayName”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of UserAssessmentSummary

Return type:

Response

Example:

Click here to see an example of how to use list_user_assessments API.

list_users(user_assessment_id, **kwargs)

Gets a list of users of the specified user assessment. The result contains the database user details for each user, such as user type, account status, last login time, user creation time, authentication type, user profile, and the date and time of the latest password change. It also contains the user category derived from these user details as well as privileges granted to each user.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • compartment_id_in_subtree (bool) – (optional) Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are returned. Depends on the ‘accessLevel’ setting.
  • access_level (str) –

    (optional) Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

    Allowed values are: “RESTRICTED”, “ACCESSIBLE”

  • user_category (str) – (optional) A filter to return only items that match the specified user category.
  • user_key (str) – (optional) A filter to return only items that match the specified user key.
  • account_status (str) – (optional) A filter to return only items that match the specified account status.
  • authentication_type (str) – (optional) A filter to return only items that match the specified authentication type.
  • user_name (str) – (optional) A filter to return only items that match the specified user name.
  • target_id (str) – (optional) A filter to return only items that match the specified target.
  • time_last_login_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose last login time in the database is greater than or equal to the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • time_last_login_less_than (datetime) –

    (optional) A filter to return users whose last login time in the database is less than the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_user_created_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose creation time in the database is greater than or equal to the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_user_created_less_than (datetime) –

    (optional) A filter to return users whose creation time in the database is less than the date and time specified, in the format defined by RFC3339. Example: 2016-12-19T16:39:57.600Z

  • time_password_last_changed_greater_than_or_equal_to (datetime) –

    (optional) A filter to return users whose last password change in the database is greater than or equal to the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • time_password_last_changed_less_than (datetime) –

    (optional) A filter to return users whose last password change in the database is less than the date and time specified, in the format defined by RFC3339.

    Example: 2016-12-19T16:39:57.600Z

  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • sort_order (str) –

    (optional) The sort order to use, either ascending (ASC) or descending (DESC).

    Allowed values are: “ASC”, “DESC”

  • sort_by (str) –

    (optional) The field to sort by. You can specify only one sort order (sortOrder). The default order for userName is ascending.

    Allowed values are: “userName”, “userCategory”, “accountStatus”, “timeLastLogin”, “targetId”, “timeUserCreated”, “authenticationType”, “timePasswordChanged”

  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of UserSummary

Return type:

Response

Example:

Click here to see an example of how to use list_users API.

list_work_request_errors(work_request_id, **kwargs)

Gets a list of errors for the specified work request.

Parameters:
  • work_request_id (str) – (required) The OCID of the work request.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of WorkRequestError

Return type:

Response

Example:

Click here to see an example of how to use list_work_request_errors API.

list_work_request_logs(work_request_id, **kwargs)

Gets a list of log entries for the specified work request.

Parameters:
  • work_request_id (str) – (required) The OCID of the work request.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of WorkRequestLogEntry

Return type:

Response

Example:

Click here to see an example of how to use list_work_request_logs API.

list_work_requests(compartment_id, **kwargs)

Gets a list of work requests.

Parameters:
  • compartment_id (str) – (required) A filter to return only resources that match the specified compartment OCID.
  • operation_type (str) – (optional) A filter to return only work requests that match the specific operation type.
  • resource_id (str) – (optional) A filter to return only work requests that match the specified resource OCID.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • page (str) –

    (optional) For list pagination. The page token representing the page at which to start retrieving results. It is usually retrieved from a previous “List” call. For details about how pagination works, see List Pagination.

  • limit (int) –

    (optional) For list pagination. The maximum number of items to return per page in a paginated “List” call. For details about how pagination works, see List Pagination.

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of WorkRequestSummary

Return type:

Response

Example:

Click here to see an example of how to use list_work_requests API.

refresh_security_assessment(security_assessment_id, run_security_assessment_details, **kwargs)

Runs a security assessment, refreshes the latest assessment, and saves it for future reference. The assessment runs with a securityAssessmentId of type LATEST. Before you start, first call the ListSecurityAssessments operation with filter “type = latest” to get the security assessment id for the target’s latest assessment.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • run_security_assessment_details (oci.data_safe.models.RunSecurityAssessmentDetails) – (required) Details to create an on-demand saved security assessment.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use refresh_security_assessment API.

refresh_user_assessment(user_assessment_id, run_user_assessment_details, **kwargs)

Refreshes the latest assessment and saves it for future reference. This operation runs with a userAssessmentId of type LATEST. Before you start, first call the ListUserAssessments operation with filter “type = latest” to get the user assessment ID for the target’s latest assessment.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • run_user_assessment_details (oci.data_safe.models.RunUserAssessmentDetails) – (required) The details required to create an on-demand saved user assessment.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use refresh_user_assessment API.

set_security_assessment_baseline(security_assessment_id, **kwargs)

Sets the saved security assessment as the baseline in the compartment where the the specified assessment resides. The security assessment needs to be of type ‘SAVED’.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • base_line_details (oci.data_safe.models.SecurityAssessmentBaseLineDetails) – (optional) Details of security assessment that need to be updated while setting the baseline.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use set_security_assessment_baseline API.

set_user_assessment_baseline(user_assessment_id, **kwargs)

Sets the saved user assessment as the baseline in the compartment where the specified assessment resides. The user assessment needs to be of type ‘SAVED’.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • base_line_details (oci.data_safe.models.UserAssessmentBaseLineDetails) – (optional) Details of user assessment that need to be updated while setting the baseline.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use set_user_assessment_baseline API.

unset_security_assessment_baseline(security_assessment_id, **kwargs)

Removes the baseline setting for the saved security assessment. The saved security assessment is no longer considered a baseline. Sets the if-match parameter to the value of the etag from a previous GET or POST response for that resource.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use unset_security_assessment_baseline API.

unset_user_assessment_baseline(user_assessment_id, **kwargs)

Removes the baseline setting for the saved user assessment. The saved user assessment is no longer considered a baseline. Sets the if-match parameter to the value of the etag from a previous GET or POST response for that resource.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use unset_user_assessment_baseline API.

update_data_safe_private_endpoint(data_safe_private_endpoint_id, update_data_safe_private_endpoint_details, **kwargs)

Updates one or more attributes of the specified Data Safe private endpoint.

Parameters:
  • data_safe_private_endpoint_id (str) – (required) The OCID of the private endpoint.
  • update_data_safe_private_endpoint_details (oci.data_safe.models.UpdateDataSafePrivateEndpointDetails) – (required) The details used to update a Data Safe private endpoint.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_data_safe_private_endpoint API.

update_on_prem_connector(on_prem_connector_id, update_on_prem_connector_details, **kwargs)

Updates one or more attributes of the specified on-premises connector.

Parameters:
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • update_on_prem_connector_details (oci.data_safe.models.UpdateOnPremConnectorDetails) – (required) The details used to update a on-premises connector.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_on_prem_connector API.

update_on_prem_connector_wallet(update_on_prem_connector_wallet_details, on_prem_connector_id, **kwargs)

Updates the wallet for the specified on-premises connector to a new version.

Parameters:
  • update_on_prem_connector_wallet_details (oci.data_safe.models.UpdateOnPremConnectorWalletDetails) – (required) The details used to update an on-premises connector’s wallet.
  • on_prem_connector_id (str) – (required) The OCID of the on-premises connector.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_on_prem_connector_wallet API.

update_security_assessment(security_assessment_id, update_security_assessment_details, **kwargs)

Updates one or more attributes of the specified security assessment. This operation allows to update the security assessment displayName, description, or schedule.

Parameters:
  • security_assessment_id (str) – (required) The OCID of the security assessment.
  • update_security_assessment_details (oci.data_safe.models.UpdateSecurityAssessmentDetails) – (required) The information to be updated.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_security_assessment API.

update_target_database(target_database_id, update_target_database_details, **kwargs)

Updates one or more attributes of the specified Data Safe target database.

Parameters:
  • target_database_id (str) – (required) The OCID of the Data Safe target database.
  • update_target_database_details (oci.data_safe.models.UpdateTargetDatabaseDetails) – (required) Details used to update the target database in Data Safe.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_target_database API.

update_user_assessment(user_assessment_id, update_user_assessment_details, **kwargs)

Updates one or more attributes of the specified user assessment. This operation allows to update the user assessment displayName, description, or schedule.

Parameters:
  • user_assessment_id (str) – (required) The OCID of the user assessment.
  • update_user_assessment_details (oci.data_safe.models.UpdateUserAssessmentDetails) – (required) The information to be updated.
  • opc_request_id (str) – (optional) Unique identifier for the request.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use update_user_assessment API.