TrustInSoft Analyzer vs. Splint

TrustInSoft has developed a source code analysis tool known as TrustInSoft Analyzer, which meticulously evaluates C and C++ code, providing mathematical assurances that defects are absent, software components are shielded from prevalent security vulnerabilities, and the code adheres to specified requirements. This innovative technology has gained recognition from the National Institute of Standards and Technology (NIST), marking it as the first globally to fulfill NIST’s SATE V Ockham Criteria, which underscores the significance of high-quality software. What sets TrustInSoft Analyzer apart is its implementation of formal methods—mathematical techniques that facilitate a comprehensive examination to uncover all potential vulnerabilities or runtime errors while ensuring that only genuine issues are flagged. Organizations utilizing TrustInSoft Analyzer have reported a significant reduction in verification expenses by 4 times, a 40% decrease in the efforts dedicated to bug detection, and they receive undeniable evidence that their software is both secure and reliable. In addition to the tool itself, TrustInSoft’s team of experts is ready to provide clients with training, ongoing support, and various supplementary services to enhance their software development processes. Furthermore, this comprehensive approach not only improves software quality but also fosters a culture of security awareness within organizations.

The Secure Programming Group within the Department of Computer Science at the University of Virginia is charged with both the creation and continual enhancement of Splint, a static analysis tool. Leading this initiative is David Evans, who is also the primary developer of the project. The initial concept of memory bounds checking was introduced by David Larochelle, while University of Virginia students such as Chris Barker, David Friedman, Mike Lanouette, and Hien Phan made notable contributions to the project's advancement. Splint is essentially an evolution of LCLint, a tool that emerged from a collaborative research project involving the Massachusetts Institute of Technology and Digital Equipment Corporation's System Research Center. David Evans also played a pivotal role as the chief designer and developer of LCLint. The foundational idea for a static checking tool that could pinpoint inconsistencies between LCL specifications and their C implementations was conceived by John Guttag and Jim Horning. Their expertise and innovative ideas were instrumental in shaping both LCLint and its successor, Splint, thereby establishing a strong framework for developing tools that significantly improve software reliability and security. This collaborative effort highlights the importance of interdisciplinary teamwork in addressing complex programming challenges.