# OCI onboarding document

- Source: https://support.icompaas.com/support/solutions/articles/a_1791531218975526-oci-onboarding-document
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Oracle Cloud](https://support.icompaas.com/support/solutions/c_1790697859097233) › [Onboarding process](https://support.icompaas.com/support/solutions/folders/f_1791530542527458)
- Last updated: 2026-10-09
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

OCI Cloud Integration with iCompaas

1.  What are we Integrating and our goal?  
      
    

-   Suppose the customer has the Oracle Cloud environment.
    

-   Then icompaas should connect to that environment with read-only access,discover its configuration and evaluate the security and compliance controls.
    

2.  The Complete Onboarding Architecture:
    

-   Let's consider that the customer is Zato, and they already have and use the OCI Cloud.and their environment looks like as below:
    

  

-   So, to onboard the cloud , the customer clicks on the “Connect OCI Cloud ” , where at this point nothing has been authorized yet.     
      
    
-   Then the icompaas creates the integration record, where the browser calls the backend and creates the requests for the cloud account onboarding with provider==OCI Cloud.  
      
    
-   Then the iCompaas UI will be displaying the Instructions to connect the cloud,and those instructions would be as mentioned below:
    

                        To connect your OCI environment, you need:  
  
                        1.OCI Tenancy OCID  
                        2. OCI User OCID  
                        3. API Key  
                        4. API Key Fingerprint  
                        5. OCI Region  
                        6. Required IAM permissions

-    Now the important point is that the customer first needs to prepare an OCI identity with permissions for iCompaas.  
                           
    
-   And then there will be a Button named “Open OCI Console” ,by clicking on that the customer goes to the OCI Cloud Console.  
      
    
-   Then in the “OCI Cloud console” in the “identity and Security management” section,under the “domains/users”, we create a user for the iCompaas,and “name it as X”.  
      
    
-   And under that user the customer has to “create the API key(signing key)”,which after creating gives the “fingerprint key” and “private key”,for the authentication of the API’s.  
      
    
-   Then after creating the API key,the customer also gets the “Tenancy OCID” and “User OCID”,which are required to authenticate the OCI.  
      
    
-   And now the next important step is to “create the IAM permissions” , for that customer has to “create the IAM group”, and “add the iCompaas identity user” to the group and “define the IAM policies” and give the required “read permissions” and save it.  
      
    
-   Now, the customer has to return to the iCompaas and they provide the values like “Private key”, “ fingerprint key”,  “ Tenancy OCID” and “User OCID” and submit them.  
      
    
-   Then iCompaas backend calls the API’s and authenticates the OCI and reads the IAM policies and then onboards the resources which are allowed into UI successfully.

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.