本专题内容
Personal data · Risk management · AI governance · Compliance · Sovereignty
Map data flows and responsibilities
How do you build an actionable data map? Follow one processing activity from collection through copies, exports, backups and deletion. The register describes purposes, data categories, applications, providers, access, retention, owners and control evidence. The aim is to explain a decision, handle a request and verify a change. Examples concern methodology; legal classification depends on context and should be checked against original sources.
阅读指南 EN新闻观察
全部国际新闻 →已保存的标题 · 无法更新 · 最近成功获取时间 : 2026年10月22日 21:24
Waze否认收集马政府敏感数据 称严格遵守隐私政策和数据保护标准 | 精彩大马 - 精彩大马
via Google News · aggregator构建人工智能和后量子时代的数据保护能力。 - Vietnam.vn
via Google News · aggregatorWhatsApp 删除了针对客服聊天机器人的隐藏 GDPR 指令 - Pasquale Pillitteri
via Google News · aggregator荷兰数据保护局对优步处以8.25亿欧元罚款，或成《通用数据保护条例》第二大罚单 - finance.sina.com.cn
via Google News · aggregator马来西亚个人数据保护局就人工智能与个人数据保护框架征询意见 - Allen & Gledhill
via Google News · aggregator一广告公司泄露用户敏感数据，挪威监管机构开出史上最大罚单 - 搜狐
via Google News · aggregator参考资料：数据、用途与局限
文档核查日期 .
此语言版本的详细参考说明以英语提供。
| 来源与目的 | 已核实的数据或指标 | 使用方法 | 需要保留的局限 |
|---|---|---|---|
| FIRST · Traffic Light Protocol Indicate who may receive redistributed information. |
TLP 2.0 uses RED, AMBER, GREEN and CLEAR; AMBER+STRICT restricts sharing to the recipient organisation. Labels must not be translated. | Keep the marking with the information and check recipients before forwarding. Ask the source to clarify any ambiguity. | TLP is neither a formal classification nor a reuse licence. It does not guarantee content accuracy. |
| NIST · AI Risk Management Framework Organise management of AI-related risks. |
The AI RMF Core is organised around Govern, Map, Measure and Manage. It is a voluntary risk-management framework. | Define intended use, affected people and error consequences. Connect each risk to an evaluation, owner and stop or recovery mechanism. | The framework certifies neither a model nor an application. Using it does not remove the need to examine applicable requirements. |
| NIST · Privacy Framework Examine risks to people arising from data processing. |
The Privacy Framework is a voluntary privacy risk-management tool. It is distinct from a universal legal compliance checklist. | Describe actual processing: data, purposes, recipients, access and retention. Compare documents, settings and deletion or retrieval tests. | Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination. |
发布与 AI 搜索可见性
此语言版本的详细参考说明以英语提供。
Assign publication decisions to an owner
Public publication and private access require different evidence. Snippet and AI participation choices must be linked to the relevant service and property.
- Record owner, scope, effective choice and inherited publication settings.
- Protect private resources through authorisation; robots.txt publicly reveals listed paths.
- Date acceptance evidence and review documentation again when the service changes.
Compare AI controls and report data →
References reviewed
security.txt 与漏洞披露
此语言版本的详细参考说明以英语提供。
Preserve contact scope when domains change
A migration, provider delegation or subdomain change can make a disclosure channel ambiguous. Domain governance should therefore include publication and review of security.txt.
- Check each relevant host: a parent domain’s file does not automatically apply to its subdomains.
- Compare Canonical URIs with actual retrieval and document provider redirects.
- Review contacts, keys, policy and expiry when responsibility transfers; preserve older versions as history.
Read the security.txt reference and disclosure cases →
Sources checked on · IETF · RFC 9116 · §2.5, §3, §5