云端保护
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
分析和审核
在应用可供下载之前，我们会分析并审核应用及其开发者。借助自动检测机制（例如机器学习）和人工分析师，我们会尽一切努力确保 Google Play 中显示的应用对用户或其设备不有害。
开发者审核
作为开发者，您必须同意 Google Play 开发者分发协议，才能向 Google Play 提交应用。
此合同旨在指导我们在 Google Play 上发布应用的开发者应遵守的行为。
此外，Google Play 还会使用各种方法来检查开发者是否遵守这些政策。Google Play 的内部风险引擎会分析开发者 Google 帐号中的信息、操作、历史记录、结算明细、设备信息等。
如果发现可疑情况，我们会人工审核相应交易，以确保开发者遵守相关规定。
内部应用审核
应用会进入审核流程，以确认其符合 Google Play 政策，然后才能在 Google Play 上架。Google 开发了一款自动化应用风险分析器，可对应用执行静态和动态分析，以检测潜在有害应用 (PHA) 行为。当 Google 的应用风险分析器发现可疑内容时，它会标记应用并将其交由安全分析师进行人工审核。
Google Play 之外的应用评价
无论来源是什么，我们都会尽力保护用户免受 PHA 和移动垃圾软件 (MUwS) 的侵扰，因此我们的系统必须分析尽可能多的应用并收集相关数据，这一点非常重要。应用是由安全研究人员、用户以及通过抓取互联网和检查来自其他市场的已安装应用找到的其他用户报告的。
用户可以在其设备上的 Google Play 保护机制中启用改进有害应用检测功能，以允许 Google 审核新应用。启用此功能有助于 Google 分析更多应用，我们的系统分析的应用越多，Google Play 保护机制在识别和限制 PHA 对所有设备的影响方面就越好。
机器学习
Play 保护机制利用 Google 强大的机器学习算法来防范 PHA。Google 的系统会通过分析整个应用数据库来了解哪些应用是有害的，哪些是安全的。这些算法会分析数百种信号并比较整个 Android 生态系统的行为，以了解是否有任何应用出现可疑行为，例如以意想不到的方式与设备上的其他应用交互、在未经授权的情况下访问或分享个人数据、恶意安装应用（包括 PHA）、访问恶意网站或绕过内置安全功能。这些算法还有助于我们了解 PHA 的来源及其创收方式，以便我们能够确定这类应用背后的动机。
以下是我们用来教机器识别良好和不良行为的一些工具。
静态分析系统会分析应用的代码，提取功能，并将其与预期的良好行为和潜在的不良行为进行比较。
第三方报告GPP 与业界和学术安全研究人员培养积极的关系。这些研究人员通过各种方式评估应用，并发送关于其发现结果的反馈。
签名GPP 使用签名将应用与包含已知不良应用和漏洞的数据库进行比较。
开发者关系GPP 会分析非代码功能，以确定应用之间可能存在的关系，并评估创建应用的开发者是否与 PHA 的创建相关联。
动态分析GPP 运行应用以识别静态分析无法检测到的互动行为。这样，审核人员就可以识别需要访问服务器和下载动态代码时的攻击。
启发词语和相似度分析GPP 会对应用进行比较，以找出识别有害应用的趋势。
SafetyNetSafetyNet 是一个可保护隐私的传感器网络，它覆盖 Android 生态系统，可识别可能危害设备的应用和其他威胁。
应用分类
对应用进行分析后，GPP 会按照“安全无害”的等级对应用进行分类。
标记为安全的应用和应用更新会采用 Google Play。
系统会屏蔽标记为有害的应用。如果审核算法不清楚应用是安全还是有害，就会被标记为“可能有害”。
Android 安全团队成员会人工审核 PHA。故意执行恶意操作的开发者将被禁止，并且无法再在 Google Play 上发布应用。
持续保护
在用户安装应用后，GPP 会继续保护用户，即使应用是从 Google Play 以外的地方下载的也不例外。
GPP 的设备端保护功能会扫描和分析设备上的每个应用。
了解详情
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-26。
[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eGoogle Play employs automated and manual reviews to ensure app safety before and after they are available for download.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Play Protect utilizes machine learning to identify and mitigate harmful apps by analyzing app behavior and comparing it against known threats.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers are subject to review and must adhere to the Google Play Developer Distribution Agreement to publish apps.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Play Protect safeguards users by continuously scanning installed apps, regardless of their source, for potentially harmful behavior.\u003c/p\u003e\n"],["\u003cp\u003eGoogle encourages users to enable "Improve harmful app detection" to enhance the system's ability to identify and protect against threats.\u003c/p\u003e\n"]]],["Google Play uses automated mechanisms and human analysts to review apps and developers before they are available for download. This includes developer account analysis, internal app review with static and dynamic methods, and data collection from various sources. Machine learning algorithms, leveraging tools like static and dynamic analysis, third-party reports, signatures, developer relationships, and SafetyNet, identify potentially harmful apps. Analyzed apps are classified and either approved or blocked. This ongoing protection extends to apps installed from outside Google Play.\n"],null,["# Cloud-based protections\n\nAnalysis and review\n-------------------\n\nBefore an app becomes available for download in Google Play we analyze and\nreview the app and its developers. Using automated detection mechanisms (for\nexample, machine learning) and human analysts, we make every effort to ensure\nthe apps that appear in Google Play aren't harmful to users or their\ndevices.\n\n### Developer review\n\nAs a developer, you must agree to the Google Play [Developer\nDistribution Agreement](https://play.google.com/about/developer-distribution-agreement.html) before you can submit your apps to Google Play.\nThis contract is a guide to the behavior we expect of developers who publish\napps in Google Play.\n\nAdditionally, Google Play uses a variety of methods to check that developers\nare complying with these policies. Google Play's internal risk engine analyzes\ninformation from a developer's Google account, actions, history, billing\ndetails, device information, and more.\nIf something suspicious turns up, we manually review the transactions to\nensure that the developer is compliant.\n\n### Internal app review\n\nApplications undergo a review process to confirm that they comply with Google\nPlay policies before they become available in Google Play. Google has developed\nan automated application risk analyzer that performs static and dynamic analysis\nof apps to detect Potentially Harmful Application (PHA) behavior. When Google's\napplication risk analyzer discovers something suspicious, it flags the app and\nrefers it to a security analyst for manual review.\n\n### App review outside of Google Play\n\nBecause we try to protect users from PHAs and mobile unwanted software (MUwS)\nregardless of the source, it's important that our systems analyze and collect\ndata on as many apps as possible. Apps are reported by security researchers, users, and others\nwe find by crawling the internet and inspecting installed apps from other\nmarkets.\n\nUsers can allow Google to review new apps by enabling the *Improve harmful\napp detection* feature in Google Play Protect on their device. Enabling this\nfeature helps Google to analyze more apps and the more apps our systems analyze,\nthe better Google Play Protect is at identifying and limiting the impact of PHAs\nfor all devices.\n\nMachine learning\n----------------\n\nPlay Protect leverages Google's powerful machine learning algorithms to\ncombat PHAs. Google's systems learn which apps are harmful and which are safe by\nanalyzing our entire app database. The algorithms look at hundreds of signals\nand compare behavior across the Android ecosystem to see if any apps show\nsuspicious behavior, such as interacting with other apps on the device in\nunexpected ways, accessing or sharing personal data without authorization,\naggressively installing apps (including PHAs), accessing malicious websites, or\nbypassing built-in security features. These algorithms also help us understand\nwhere PHAs come from and how they make money, so we can determine the motivation\nbehind these types of apps.\n\nHere are some of the tools we use to teach machines to identify good and bad\nbehavior. \n**Static analysis**\n\nThe app's code is analyzed and the features are\nextracted and compared against expected good behavior and potential bad behavior. \n**Third-party reports**\n\nGPP cultivates active\nrelationships with industry and academic security researchers. These researchers\nevaluate apps in a variety of ways and send in feedback regarding their findings. \n**Signatures**\n\nGPP uses signatures to compare apps against a\ndatabase of known bad apps and vulnerabilities. \n**Developer relationships**\n\nGPP analyzes non-code features to\ndetermine possible relationships between applications and to evaluate\nwhether the developer that created the application has been associated\nwith the creation of PHAs. \n**Dynamic analysis**\n\nGPP runs applications to identify interactive\nbehavior that can't be seen with static analysis. This allows reviewers\nto identify attacks that require server access and dynamic code downloading. \n**Heuristic and similarity analysis**\n\nGPP compares applications\nto find trends that identify harmful apps. \n**SafetyNet**\n\nSafetyNet is a privacy preserving sensor\nnetwork that spans the Android ecosystem and identifies apps and\nother threats that can harm devices.\n\nClassifying apps\n----------------\n\nAfter analyzing the apps, GPP classifies them on a scale of safe to harmful.\nApps and app updates that are marked as safe are adopted into Google Play.\nApps that are marked as harmful are blocked. If the review algorithms are\nunclear whether an app is safe or harmful, it's marked as potentially harmful.\nAndroid Security Team members review PHAs manually. Developers who knowingly\nperform malicious actions are banned and can no longer publish apps on Google Play.\n\nOngoing protection\n------------------\n\nGPP continues protecting users after they've installed an app,\neven if the is app downloaded from outside of Google Play.\nGPP's on-device protections scan and analyze every app on the device.\n\n\n[Learn more](/android/play-protect/client-protections)"]]
