Dropbox uploaded files not determined correctly

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

Dropbox uploaded files not determined correctly

L1 Bithead

Hello, after implementing SSL decryption we're trying to improve visibility and noticed that files to dropbox web aren't shown correctly

 

When downloading from the dropbox website, the file names are correctly shown, but when uploading the files are registered in the data filtering logs as "presentation.xml" and "put_block_returning_token"

 

Tried this on Palo 9.1 and 10.1 and from chrome and mozilla

 

Is there a workaround to this that would let us see what users are uploading?

 

Thank you!

1 accepted solution

Accepted Solutions

Community Team Member

Hi @Megrretz ,

 

I believe it's a limitation caused by how Dropbox works:

The payload or packet in which the file is being uploaded to Dropbox is a new connection with no filename in it but with name "put_block_returning_token_unauth".  Once the upload is done, dropbox updates the filename in the initial connection which has no data.  

 

Because there is no filename in the connection in which data is being uploaded, the firewall cannot identify the correct filename.

 

Compared to Dropbox download, the filename and data are in same connection and same packet hence, filename would be identified correctly.

 

Cheers,

-Kiwi.

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

2 REPLIES 2

Community Team Member

Hi @Megrretz ,

 

I believe it's a limitation caused by how Dropbox works:

The payload or packet in which the file is being uploaded to Dropbox is a new connection with no filename in it but with name "put_block_returning_token_unauth".  Once the upload is done, dropbox updates the filename in the initial connection which has no data.  

 

Because there is no filename in the connection in which data is being uploaded, the firewall cannot identify the correct filename.

 

Compared to Dropbox download, the filename and data are in same connection and same packet hence, filename would be identified correctly.

 

Cheers,

-Kiwi.

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

That's what Palo support said as well. Too bad!

 

Thank you

  • 1 accepted solution
  • 2172 Views
  • 2 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!