During license audit projects, we have frequently collaborated with our customers to collect datasets in Excel spreadsheets containing several hundred thousand rows. To make them manageable for the respective projects, we then had to shorten them to suit the specific requirements. Is the software by Autodesk? Then its importance is secondary for a Microsoft project. Is it maybe open source? In this case it is irrelevant for an Adobe audit.
The question of what exactly happens next with the culled data was frequently outsourced to a follow-on project or placed conveniently into the category of “we’ll deal with that when we have the time”. But on no accounts should the risks to ongoing operations be underestimated: from IKEA kitchen planners in the admin department, to Steam and PlayStation clients on production PCs and even unauthorized browser add-ons in an R&D setting, we’ve found pretty much every kind of software in just as many environments.
Here, programs that transmit information from the company and, to do so, work their way around the internal firewalls, are among the most dangerous. Sounds logical? But almost every web application uses this ploy. This is because they operate via the external port 80. These ports are the interface between the programs and the operating systems. In this case, number 80 is reserved for applications that use the Hypertext Transfer Protocol (HTTP). Applications are allowed to communicate in both directions. In a nutshell: a large number of uncontrolled Internet applications present a significant security risk.