By Dee A. Ware
While there are prescribed standards for conducting several types of audits, external software license audits remain unregulated and ripe for legislative intervention. Until then, companies must fend for themselves. From our experience, a software publisher’s motivation to conduct an audit falls into at least one of the following buckets:
From a legal perspective, the first line of defense is to negotiate a license agreement that contains clear definitions, such as, what constitutes “use” of a license, who qualifies as a “user,” the environment where the software can be deployed and, if applicable, how the software can be incorporated, marketed, sold or distributed. Once the parameters are established, the company should adopt internal processes to ensure compliance. In the absence of federal or state regulation, the parties to a licensing agreement can also agree in advance how a software audit is to be conducted, allowing the company to negotiate terms that offer some protection from unreasonable demands or spurious results. For example, the audit provision in the license agreement can address:
Lastly, what should a company do if the software publisher demands an audit? Remember that the best defense is (sometimes) a good offense. The company should not automatically capitulate to an audit request without first seeking legal counsel to evaluate the applicable audit provision and guide the company through the process to minimize exposure and reduce the risk of subsequent litigation.
0 Comments
|
By Tactical Law Attorneys and From Time to Time Their Guests
|