Cortex Data Lake Integration Migration

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cortex Data Lake Integration Migration

L2 Linker

Hi everyone,

 

Need your help in understanding the Cortex Data Lake integration migration request. We have received a notification indicating that the Cortex XDR request for migrating the Cortex Data Lake integration directly into Cortex XDR. Should we migrate manually or should we just wait for automatic migration without doing anything. Please provide information on the pros and cons of proceeding with it.

1 accepted solution

Accepted Solutions

L5 Sessionator

Hello @aungzaymyo ,

 

Thanks for reaching out on LiveCommunity!

You are receiving this message because in order to simplify Palo Alto Network devices security logs ingestion into XDR our product team has natively integrated a dedicated data lake within the Cortex XDR tenant itself. This removes the need for separate configuration of Cortex Data Lake. Hence existing integrations should be migrated to the Cortex Native Data Lake. Integrations not migrated manually will be migrated automatically 2 weeks before the end of the contract with Cortex Data Lake.

With CDL separation, if you are only using CDL for log ingestion into XDR then you can either manually migrate or wait for the automatic migration as mentioned above. However, if you are using CDL for other purposes then you need to plan for it. Because CDL service will not be available after expiration date if you do not have a separate standalone license for CDL which you can renew further.

The migration process should be smooth. If you face any problem please raise a support case.

Please follow below document if you want to have manual migration.

https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-Pro-Administrator-Guide/Ingest-Data...

 

If you feel this has answered your query, please let us know by clicking on "mark this as a Solution". Thank you.

Ashutosh Patil

View solution in original post

1 REPLY 1

L5 Sessionator

Hello @aungzaymyo ,

 

Thanks for reaching out on LiveCommunity!

You are receiving this message because in order to simplify Palo Alto Network devices security logs ingestion into XDR our product team has natively integrated a dedicated data lake within the Cortex XDR tenant itself. This removes the need for separate configuration of Cortex Data Lake. Hence existing integrations should be migrated to the Cortex Native Data Lake. Integrations not migrated manually will be migrated automatically 2 weeks before the end of the contract with Cortex Data Lake.

With CDL separation, if you are only using CDL for log ingestion into XDR then you can either manually migrate or wait for the automatic migration as mentioned above. However, if you are using CDL for other purposes then you need to plan for it. Because CDL service will not be available after expiration date if you do not have a separate standalone license for CDL which you can renew further.

The migration process should be smooth. If you face any problem please raise a support case.

Please follow below document if you want to have manual migration.

https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-Pro-Administrator-Guide/Ingest-Data...

 

If you feel this has answered your query, please let us know by clicking on "mark this as a Solution". Thank you.

Ashutosh Patil
  • 1 accepted solution
  • 2961 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!