Steve
Established Member
Hi Chaps,
My word - we really are getting down to it here!
Neil is absolutely correct, because we agree that the definition of 'secure' on the web means that data is encrypted and stored on an httpS server. We agree therefore that the name and address details are not secure.
What I have been labouring to explain is that in the context of the entire transaction process, from placing the order, providing details and card details, the system we designed breaks this information up and processes and stores in different places. As far as I am aware, no other woodworking sites have gone to these lengths. It is, by comparison, 'super' secure.
In designing a secure system, you have to define the process and apply appropiate levels of security to the various stages of that process.
This is precisely what we have done on the shopping system for Stiles and Bates.
The problem we have here is that my good friends on the forum are labouring under the impression that name and address details should be treated with the same level of security as card numbers.
There is no reason whatsoever to do this because these details are defined 'open' or 'PD' (Public domain).
Actually - let me refine that statement. There is only ONE reason to encrypt name and address details - to dupe the customer into a FALSE sense of security as far as name and addresses are concerned!
Many shopping systems take all the details at once and place them all on the same server at the same time. This level of security is certainly high enough. Our system takes it a couple of levels higher - it should be serving as the security benchmark for the list!
Steve
My word - we really are getting down to it here!
Neil is absolutely correct, because we agree that the definition of 'secure' on the web means that data is encrypted and stored on an httpS server. We agree therefore that the name and address details are not secure.
What I have been labouring to explain is that in the context of the entire transaction process, from placing the order, providing details and card details, the system we designed breaks this information up and processes and stores in different places. As far as I am aware, no other woodworking sites have gone to these lengths. It is, by comparison, 'super' secure.
In designing a secure system, you have to define the process and apply appropiate levels of security to the various stages of that process.
This is precisely what we have done on the shopping system for Stiles and Bates.
The problem we have here is that my good friends on the forum are labouring under the impression that name and address details should be treated with the same level of security as card numbers.
There is no reason whatsoever to do this because these details are defined 'open' or 'PD' (Public domain).
Actually - let me refine that statement. There is only ONE reason to encrypt name and address details - to dupe the customer into a FALSE sense of security as far as name and addresses are concerned!
Many shopping systems take all the details at once and place them all on the same server at the same time. This level of security is certainly high enough. Our system takes it a couple of levels higher - it should be serving as the security benchmark for the list!
Steve