Will there be any encryption between source and destination?

Because the source and the destination sync happens in the same process, encryption isn’t such a problem (unless you can think of a reason it is). However if we start having a queuing mechanism in between that is something we will think about. What do you think?

If we have PII data going between an Oracle source (unencrypted) to a Snowflake target how do we ensure the network packets can't be sniffed to pull out SSN's? Something like this would be bad:

@Michel Many BigCo's have 1+ people responsible for security, that act as a gatekeeper (i.e. their approval is required for Airbyte's adoption). They usually have a standard checklist of requirements and reasons why each checklist item exists. If interested in planning for BigCo adoption (you might not be at this time!), it might be worth reaching out to a few to discuss their checklists and see what compliance may look like (I don't have anyone I can volunteer to you, sorry!)

@Cody K. I see. that's not good indeed. In your case, do you know why it isn't encrypted when pulling data out of Oracle? I think this is something we could offer as an option in the oracle connector. If we think of the 3 places where data could be un-encrypted in transit that would be: 1. oracle -> airbyte source: I am going to assume there is a way in oracle to configure some encryption when readers request data 2. airybte source -> airbyte destination: this is airbyte responsibility here to ensure encryption, right now it is not a problem since it all happens in the same process but that will change once AB source and AB destination start communicating over the network or with a queue in the middle. We will need to take that into account when we split the communication to be across separate processes 3. airbyte destination -> Snowflake: here I would like to assume that it is also possible to open an encrypted connection to snowflake. Does that make sense to you?

i'm really intersted to know where i can find updated response to this question @User