Application Inspector是微软开源的软件特征源码的安全分析工具。可以通过使用静态分析和可自定义的基于 json 的规则引擎来识别软件源码特征，了解程序的功能。Application Inspector工具包含一个可过滤的置信度指示器,会根据 500 多种规则模式报告发现的内容，并进行特征检测，包括影响安全性的特征，例如安全加密技术的使用, 应用程序框架（开发、测试）, 云/服务 API（Microsoft Azure、Amazon AWS 和 Google Cloud Platform） ,密码学相关（对称、非对称、哈希和 TLS）, 数据类型（敏感的个人身份信息）, 操作系统功能（平台标识、文件系统、注册表和用户帐户）等方面。Application Inspector遵守MIT开源协议。
[repo owner=”Microsoft” name=”ApplicationInspector”]
-----------------------------------------------------------------
A source code analyzer built for surfacing characteristics to answer the question 'What's in the code?' quickly using static analysis with a json based rules engine. Ideal for scanning components before use.
Introduction
Microsoft Application Inspector is a software source code characterization tool that helps identify coding features of first or third party software components based on well-known library/API calls and is helpful in security and non-security use cases. It uses hundreds of rules and regex patterns to surface interesting characteristics of source code to aid in determining what the software is or what it does from what file operations it uses, encryption, shell operations, cloud API's, frameworks and more and has received industry attention as a new and valuable contribution to OSS on ZDNet, SecurityWeek , CSOOnline , Linux.com/news , HelpNetSecurity, Twitter and more and was first featured on Microsoft.com.
Application Inspector is different from traditional static analysis tools in that it doesn't attempt to identify "good" or "bad" patterns; it simply reports what it finds against a set of over 400 rule patterns for feature detection including features that impact security such as the use of cryptography and more. This can be extremely helpful in reducing the time needed to determine what Open Source or other components do by examining the source directly rather than trusting to limited documentation or recommendations.
The tool supports scanning various programming languages including C, C++, C#, Java, JavaScript, HTML, Python, Objective-C, Go, Ruby, PowerShell and more and can scan projects with mixed language files. It supports generating results in HTML, JSON and text output formats with the default being an HTML report similar to the one shown here.
Be sure to see our complete project wiki page https://Github.com/Microsoft/ApplicationInspector/wiki for additional information and help.
Quick Start
Obtain Application Inspector
.NET Tool (recommended)
- Download and install the .NET 6 SDK
- Run
dotnet tool install --global Microsoft.CST.ApplicationInspector.CLI
See more in the wiki
Platform Dependent Binary
- Download Application Inspector by selecting the pre-built package for the operating system of choice shown under the Assets section of the Releases.
Run Application Inspector
- Nuget Tool:
appinspector analyze -s path/to/src. - Platform Specific:
applicationinspector.cli.exe analyze -s path/to/src
Goals
Microsoft Application Inspector helps you in securing your applications from start to deployment.
Design Choices - Enables you to choose which components meet your needs with a smaller footprint of unnecessary or unknowns features for keeping your application attack surface smaller as well as help to verify expected ones i.e. industry standard crypto only.
Identifying Feature Deltas - Detects changes between component versions which can be critical for detecting injection of backdoors.
Automating Security Compliance Checks - Use to identify components with features that require additional security scrutiny, approval or SDL compliance as part of your build pipeline or create a repository of metadata regarding all of your enterprise application.
Contribute
We have a strong default starting base of Rules for feature detection. But there are many feature identification patterns yet to be defined and we invite you to submit ideas on what you want to see or take a crack at defining a few. This is a chance to literally impact the open source ecosystem helping provide a tool that everyone can use. See the Rules section of the wiki for more.
Official Releases
Application Inspector is in GENERAL AUDIENCE release status. Your feedback is important to us. If you're interested in contributing, please review the CONTRIBUTING.md.
Application Inspector is availble as a command line tool or NuGet package and is supported on Windows, Linux, or MacOS.
Platform specific binaries of the ApplicationInspector CLI are available on our GitHub releases page.
The C# library is available on NuGet as Microsoft.CST.ApplicationInspector.Commands .
The .NET Global Tool is available on NuGet as Microsoft.CST.ApplicationInspector.CLI.
If you use the .NET Core version, you will need to have .NET 6.0 or later installed. See the JustRunIt.md or Build.md files for more.
CLI Usage Information
> appinspector --help
ApplicationInspector.CLI 1.8.4-beta+976ee3cdd1
c Microsoft Corporation. All rights reserved.
analyze Inspect source directory/file/compressed file (.tgz|zip)
against defined characteristics
tagdiff Compares unique tag values between two source paths
exporttags Export the list of tags associated with the specified rules.
Does not scan source code.
verifyrules Verify custom rules syntax is valid
packrules Combine multiple rule files into one file for ease in
distribution
help Display more information on a specific command.
version Display version information.
Examples:
Command Help
To get help for a specific command run appinspector <command> --help.
Analyze Command
The Analyze Command is the workhorse of Application Inspector.
Simple Default Analyze
This will produce an output.html of the analysis in the current directory using default arguments and rules.
appinspector analyze -s path/to/files
Output Sarif
appinspector analyze -s path/to/files -f sarif -o output.sarifExcluding Files using Globs
This will create a json output named data.json of the analysis in the current directory, excluding all files in test and .git folders using the provided glob patterns.
appinspector analyze -s path/to/files -o data.json -f json -g **/tests/**,**/.git/**
Additional Usage Information
For additional help on use of the console interface see CLI Usage.
For help using the NuGet package see NuGet Support
Build Instructions
See build.md
from
