Customers
Case Studies
Case Study 2 - What's In The Box?
As companies grow, engineering decisions and the reasoning behind them can be lost as the engineers, designers and coders who built the product come and go. In high employee turnover environments, there often remains very little detail about the actual architecture of the product in the corporate memory. This becomes important when you examine how some products are developed: Someone gets an idea and grabs a couple of pieces of code from the Internet to see if their idea will work. The enterprising group will write some software that “glues” the open source tools together to form a new product - the intent being to write new code to replace the prototype down the road. Only that never happens…
The Security Consortium™ (TSC) was approached by a company in such a position. A security startup had gone through a complete personnel turnover while they were negotiating another round of financing. Subsequently, this new group of entrepreneurs had no idea what was at the core of their product, leaving them open to claims of potential litigation.
At TSC, we put the product in our lab and ran it through the TSC proprietary testing processes. The results helped the new management team uncover some decisions that they didn't know prior developers had made. As such, the company can make an informed decision on licensing and re-coding parts of its product to avoid possible claims of infringement. In addition, TSC identified numerous areas where the product could be enhanced to increase its security posture and better serve its target customers.
TSC helped this company discover the technology inside its product, and advised them on ways to avoid litigation while improving the overall operation and the posture of the product.