The use of artificial intelligence (AI) in organisations is increasingly widespread, thanks to its ability to increase efficiency, reduce the time that needs to be dedicated to more menial tasks, and rapidly solve complex problems.

But, as with any emerging technology, AI’s growth in popularity establishes a new attack surface for malicious actors to exploit, thereby introducing new risks and vulnerabilities to an increasingly complex computing landscape.

Open-source software has become ubiquitous in modern software development, enabling developers to leverage and build upon existing code to create innovative solutions.

However, managing open-source licenses can be complex and time-consuming, particularly for large enterprises with hundreds or thousands of software components. To ensure compliance and reduce the risk of legal issues, some organizations implement professional tools to help them with license management for open-source plugins and components.

Although the GDPR deadline has now passed, it’s important for organisations to show that in the event of a regulatory investigation, they have taken reasonable steps to demonstrate they take privacy seriously – and ultimately comply. The good news is that fines for organisations that suffer a breach of personal data won’t be applied if they can prove they’ve taken the correct steps to comply.

The reality is that GDPR will be a continuous journey for organisations involving constantly reviewing data, removing low value data, looking at new data, following procedures, and maintaining trust with customers – by prioritising their privacy. Although many organisations are becoming better prepared for GDPR, here are some key, practical actions that must be taken now.

The Treasury Inspector General for Tax Administration said in a Sept. 18 report that the IRS prematurely closed 11 recommendations from three prior audits of the agency’s software license management.

The audits, which occurred between June 2013 and September 2014, outlined 14 recommendations to improve the tracking of software licenses across the agency’s mainframe, service, and desktop and laptop environments, including developing roles and responsibilities in the Internal Revenue Manual for managing software assets.

TIGTA officials also said that the IRS was not in compliance with the Making Electronic Government Accountable By Yielding Tangible Efficiencies, or MEGABYTE, Act of 2016 for a series of conditions it has yet to meet. The law requires agencies to create plans to manage and inventory software licenses.

For the 11 recommendations the IRS said it had taken steps to close in October 2016, investigators said the agency had not gone far enough into resolving the proposals before closing them.

Two recommendations centered on establishing an organizational structure to manage software assets and licenses. The IRS established the Enterprise Software Governance Board in December 2013 to oversee software assets, but it was decommissioned in 2015 as part of an agency organizational consolidation.

Presently, investigators say there is no organizational structure to oversee software asset management; information is sent to ex-ESGB members to resolve funding issues. Oversight issues are sent to Information Technology Infrastructure Strategy Team, an ESGB working group.

Two other recommendations called for the IRS to craft policy and guidance using the Information Technology Infrastructure Library, a recognized set of best practices for managing IT systems.

Agency officials did craft a policy for IT asset management titled IRM 2.149, but investigators said it didn’t “establish policy and guidance for IRS management as defined by the ITIL.” The report also said that the agency hadn’t written guidance of the level needed to close the recommendation.

The IRS also hasn’t created roles and responsibilities for personnel to handle software asset management or developed operating procedures for automated solutions to track software usage and costs, which represented four collective recommendations.

The agency is using an IBM-based program to track inventory, but TIGTA officials said asset management solutions should include license entitlement information.

The IRS has yet to implement software tools to fully track licensing data, and develop and maintain a software license inventory, saying that there is not one commercial-off-the-shelf tool to create an inventory. Since no tool has been implemented, TIGTA officials said a collective six recommendations should remain open.

“The IRS continues to be unable to report a complete and accurate inventory with associated costs. Until the IRS implements an effective SAM program to manage software licenses, it will continue to incur increased risks in managing software licenses,” the report said.

TIGTA officials offered three additional recommendations: