During a recent audit, I ran into something interesting while reviewing a script as part of a control related to data integrity. The script performed a simple ETL function (Extract Transform & Load) on tables of data sent and retrieved over a secure FTP connection from their customer’s server.
As I wallowed in geek heaven, deconstructing the code and the intricacies of their ETL process, I ran into a really groovy algorithm. I asked the author of the script what the algorithm was for and he said it performed a Cyclical Redundancy Check (CRC).
I remembered reading up on CRC checks while studying for the CISA, but had never encountered one in the wild. I figured now is a better time than any to dive in and learn more!
more here.......http://www.risk3sixty.com/2015/03/12/cyclical-redundancy-check-an-explanation-for-the-layman/
As I wallowed in geek heaven, deconstructing the code and the intricacies of their ETL process, I ran into a really groovy algorithm. I asked the author of the script what the algorithm was for and he said it performed a Cyclical Redundancy Check (CRC).
I remembered reading up on CRC checks while studying for the CISA, but had never encountered one in the wild. I figured now is a better time than any to dive in and learn more!
more here.......http://www.risk3sixty.com/2015/03/12/cyclical-redundancy-check-an-explanation-for-the-layman/
