Regulatory compliance

In general, compliance means conforming to a rule, such as a specification, policy, standard or law. Compliance has traditionally been explained by reference to the deterrence theory, according to which punishing a behavior will decrease the violations both by the wrongdoer (specific deterrence) and by others (general deterrence). This view has been supported by economic theory, which has framed punishment in terms of costs and has explained compliance in terms of a cost-benefit equilibrium (Becker 1968). However, psychological research on motivation provides an alternative view: granting rewards (Deci, Koestner and Ryan, 1999) or imposing fines (Gneezy Rustichini 2000) for a certain behavior is a form of extrinsic motivation that weakens intrinsic motivation and ultimately undermines compliance.

Regulatory compliance describes the goal that organizations aspire to achieve in their efforts to ensure that they are aware of and take steps to comply with relevant laws, policies, and regulations.^[1] Due to the increasing number of regulations and need for operational transparency, organizations are increasingly adopting the use of consolidated and harmonized sets of compliance controls.^[2] This approach is used to ensure that all necessary governance requirements can be met without the unnecessary duplication of effort and activity from resources.

Regulations and accrediting organizations vary among fields, with examples such as PCI-DSS and GLBA in the financial industry, FISMA for U.S. federal agencies, HACCP for the food and beverage industry, and the Joint Commission and HIPAA in healthcare. In some cases other compliance frameworks (such as COBIT) or even standards (NIST) inform on how to comply with regulations.

Some organizations keep compliance data—all data belonging or pertaining to the enterprise or included in the law, which can be used for the purpose of implementing or validating compliance—in a separate store for meeting reporting requirements. Compliance software is increasingly being implemented to help companies manage their compliance data more efficiently. This store may include calculations, data transfers, and audit trails.^[3]^[4]

^ Compliance, Technology, and Modern Finance, 11 Journal of Corporate, Financial & Commercial Law 159 (2016)
^ Silveira, P.; Rodriguez, C.; Birukou, A.; Casati, F.; Daniel, F.; D'Andrea, V.; Worledge, C.; Zouhair, T. (2012), "Aiding Compliance Governance in Service-Based Business Processes", Handbook of Research on Service-Oriented Systems and Non-Functional Properties (PDF), IGI Global, pp. 524–548, doi:10.4018/978-1-61350-432-1.ch022, hdl:11311/1029233, ISBN 9781613504321
^ Norris-Montanari, J. (27 February 2017). "Compliance – Where does it fit in a data strategy?". SAS Blogs. SAS Institute, Inc. Retrieved 31 July 2018.
^ Monica, A.D.; Shilt, C.; Rimmerman, R.; et al. (2015). "Chapter 4: Monitoring software updates". Microsoft System Center Software Update Management Field Experience. Microsoft Press. pp. 57–82. ISBN 9780735695894.

[ssrn.com-1] Compliance, Technology, and Modern Finance, 11 Journal of Corporate, Financial & Commercial Law 159 (2016)

[2] Silveira, P.; Rodriguez, C.; Birukou, A.; Casati, F.; Daniel, F.; D'Andrea, V.; Worledge, C.; Zouhair, T. (2012), "Aiding Compliance Governance in Service-Based Business Processes", Handbook of Research on Service-Oriented Systems and Non-Functional Properties (PDF), IGI Global, pp. 524–548, doi:10.4018/978-1-61350-432-1.ch022, hdl:11311/1029233, ISBN 9781613504321

[Norris-MontanariCompliance17-3] Norris-Montanari, J. (27 February 2017). "Compliance – Where does it fit in a data strategy?". SAS Blogs. SAS Institute, Inc. Retrieved 31 July 2018.

[MonicaMicrosoft15-4] Monica, A.D.; Shilt, C.; Rimmerman, R.; et al. (2015). "Chapter 4: Monitoring software updates". Microsoft System Center Software Update Management Field Experience. Microsoft Press. pp. 57–82. ISBN 9780735695894.

[1]

[2]

[3]

[4]