@marinjursic/prc-linux-arm64 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +3 -0
- package/bin/LICENSE +21 -0
- package/bin/README.md +335 -0
- package/bin/THIRD_PARTY_NOTICES.md +74 -0
- package/bin/adapters/checkov-v3.3.8.yaml +50 -0
- package/bin/adapters/gitleaks-v8.30.0.yaml +63 -0
- package/bin/adapters/grype-v0.116.1.yaml +58 -0
- package/bin/adapters/syft-v1.51.0.yaml +54 -0
- package/bin/catalog/assertions/core-repository.yaml +625 -0
- package/bin/catalog/assertions/iac.yaml +24 -0
- package/bin/catalog/assertions/supply-chain.yaml +45 -0
- package/bin/catalog/control-contracts.json +1 -0
- package/bin/catalog/control-id-registry.json +110470 -0
- package/bin/catalog/objectives/core-repository.yaml +243 -0
- package/bin/catalog/objectives/iac.yaml +13 -0
- package/bin/catalog/objectives/supply-chain.yaml +13 -0
- package/bin/catalog/profiles/api.yaml +12 -0
- package/bin/catalog/profiles/core-repository.yaml +49 -0
- package/bin/catalog/profiles/iac.yaml +18 -0
- package/bin/catalog/profiles/kubernetes.yaml +15 -0
- package/bin/catalog/profiles/quick.yaml +27 -0
- package/bin/catalog/profiles/supply-chain.yaml +20 -0
- package/bin/docs/architecture/adapters.md +380 -0
- package/bin/docs/architecture/agent-providers.md +188 -0
- package/bin/docs/architecture/applicability.md +80 -0
- package/bin/docs/architecture/catalog-integrity.md +85 -0
- package/bin/docs/architecture/evidence-and-results.md +154 -0
- package/bin/docs/architecture/execution-plans.md +61 -0
- package/bin/docs/architecture/product-contract.md +76 -0
- package/bin/docs/architecture/publisher-trust.md +68 -0
- package/bin/docs/architecture/remediation-contract.md +113 -0
- package/bin/docs/architecture/trust-model.md +95 -0
- package/bin/docs/assets/hero.svg +37 -0
- package/bin/docs/assets/logo.svg +13 -0
- package/bin/docs/assets/production-readiness-scan-demo-poster.png +0 -0
- package/bin/docs/assets/production-readiness-scan-demo.gif +0 -0
- package/bin/docs/assets/production-readiness-scan-demo.mp4 +0 -0
- package/bin/docs/assets/social-card.png +0 -0
- package/bin/docs/assets/social-card.svg +40 -0
- package/bin/docs/checklists/00-readiness-principle.md +17 -0
- package/bin/docs/checklists/01-release-foundations.md +91 -0
- package/bin/docs/checklists/02-product-risk-architecture.md +136 -0
- package/bin/docs/checklists/03-source-build-supply-chain.md +97 -0
- package/bin/docs/checklists/04-environments-quality-experience.md +226 -0
- package/bin/docs/checklists/05-application-security.md +320 -0
- package/bin/docs/checklists/06-data-privacy-performance.md +166 -0
- package/bin/docs/checklists/07-reliability-operations.md +355 -0
- package/bin/docs/checklists/08-maintenance-vendors-compliance.md +112 -0
- package/bin/docs/checklists/09-conditional-modules.md +229 -0
- package/bin/docs/checklists/10-evidence-and-decision.md +111 -0
- package/bin/docs/engineering/00-overview.md +51 -0
- package/bin/docs/engineering/01-governance-and-foundations.md +919 -0
- package/bin/docs/engineering/02-product-and-requirements.md +186 -0
- package/bin/docs/engineering/03-user-experience-web-and-content.md +1352 -0
- package/bin/docs/engineering/04-architecture-and-design.md +387 -0
- package/bin/docs/engineering/05-code-quality-and-implementation.md +1103 -0
- package/bin/docs/engineering/06-application-services-and-apis.md +476 -0
- package/bin/docs/engineering/07-data-and-information-lifecycle.md +1009 -0
- package/bin/docs/engineering/08-security-and-cryptography.md +1215 -0
- package/bin/docs/engineering/09-privacy-and-data-protection.md +205 -0
- package/bin/docs/engineering/10-verification-and-testing.md +841 -0
- package/bin/docs/engineering/11-developer-experience-platform-and-delivery.md +1013 -0
- package/bin/docs/engineering/12-operations-sre-and-support.md +795 -0
- package/bin/docs/engineering/13-documentation-and-knowledge.md +349 -0
- package/bin/docs/engineering/14-trust-safety-and-ecosystems.md +330 -0
- package/bin/docs/engineering/15-ai-ml-and-ai-assisted-development.md +785 -0
- package/bin/docs/engineering/16-specialized-domains-and-release-assurance.md +775 -0
- package/bin/docs/engineering/source-manifest.md +479 -0
- package/bin/docs/guides/ai-assisted-review.md +61 -0
- package/bin/docs/guides/getting-started.md +78 -0
- package/bin/docs/index.md +66 -0
- package/bin/docs/prompts/evidence-challenge.md +26 -0
- package/bin/docs/prompts/full-readiness-review.md +34 -0
- package/bin/docs/prompts/release-diff-review.md +31 -0
- package/bin/docs/records/evidence-record.md +42 -0
- package/bin/docs/records/go-no-go-decision.md +63 -0
- package/bin/docs/records/release-assessment.md +124 -0
- package/bin/docs/records/risk-exception.md +64 -0
- package/bin/docs/references.md +52 -0
- package/bin/docs/scanner/ai-control-review.md +208 -0
- package/bin/docs/scanner/benchmarks.md +122 -0
- package/bin/docs/scanner/cli-contract.md +130 -0
- package/bin/docs/scanner/configuration.md +101 -0
- package/bin/docs/scanner/control-contracts.md +47 -0
- package/bin/docs/scanner/core-repository.md +62 -0
- package/bin/docs/scanner/diff-and-invalidation.md +79 -0
- package/bin/docs/scanner/doctor.md +71 -0
- package/bin/docs/scanner/getting-started.md +355 -0
- package/bin/docs/scanner/go-http-timeouts.md +96 -0
- package/bin/docs/scanner/infrastructure-policy.md +64 -0
- package/bin/docs/scanner/kubernetes-workloads.md +63 -0
- package/bin/docs/scanner/mcp-agent-integration.md +138 -0
- package/bin/docs/scanner/openapi-contracts.md +75 -0
- package/bin/docs/scanner/private-key-armor.md +44 -0
- package/bin/docs/scanner/releases.md +160 -0
- package/bin/docs/scanner/remediation.md +273 -0
- package/bin/docs/scanner/risk-exceptions.md +52 -0
- package/bin/docs/scanner/security-walkthrough.md +236 -0
- package/bin/docs/scanner/state-and-history.md +113 -0
- package/bin/docs/scanner/supply-chain.md +132 -0
- package/bin/docs/scanner/test-discovery.md +60 -0
- package/bin/docs/stylesheets/extra.css +183 -0
- package/bin/fixtures/benchmarks/core-native/suite-comprehensive.yaml +302 -0
- package/bin/fixtures/benchmarks/core-native/suite.yaml +59 -0
- package/bin/fixtures/benchmarks/core-native/targets/baseline/README.md +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/baseline/app.go +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/conflict-template/app.js +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/container-risky-template/Dockerfile +2 -0
- package/bin/fixtures/benchmarks/core-native/targets/container-valid/Dockerfile +2 -0
- package/bin/fixtures/benchmarks/core-native/targets/dependency-lock-missing/package.json +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/dependency-lock-present/package-lock.json +6 -0
- package/bin/fixtures/benchmarks/core-native/targets/dependency-lock-present/package.json +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/empty-manifest-template/package.json +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/final-newline-template/app.py +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/.github/CODEOWNERS +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/.github/dependabot.yml +6 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/.github/workflows/validate.yml +15 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/CODE_OF_CONDUCT.md +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/CONTRIBUTING.md +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/LICENSE +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/README.md +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/SECURITY.md +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/package-lock.json +6 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/package.json +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/foundation-present/tests/example.test.js +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-server-timeout-risky-template/go.mod +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-server-timeout-risky-template/server.go +18 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-malformed-template/client.go +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-malformed-template/go.mod +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-risky-template/client.go +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-risky-template/go.mod +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-safe/client.go +22 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-safe/go.mod +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/go-http-timeout-safe/hazards_test.go +8 -0
- package/bin/fixtures/benchmarks/core-native/targets/kubernetes-risky-template/deployment.yaml +27 -0
- package/bin/fixtures/benchmarks/core-native/targets/kubernetes-valid/deployment.yaml +26 -0
- package/bin/fixtures/benchmarks/core-native/targets/openapi-operation-ids-risky-template/openapi.yaml +17 -0
- package/bin/fixtures/benchmarks/core-native/targets/openapi-operation-responses-risky-template/openapi.yaml +11 -0
- package/bin/fixtures/benchmarks/core-native/targets/openapi-root-malformed-template/openapi.yaml +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/openapi-root-risky-template/openapi.yaml +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/openapi-root-valid/openapi.yaml +17 -0
- package/bin/fixtures/benchmarks/core-native/targets/package-test-command/app.js +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/package-test-command/package.json +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/package-test-placeholder/app.js +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/package-test-placeholder/package.json +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/private-key-template/deploy.pem +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/readme-missing/fixture.txt +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/runtime-missing/package-lock.json +6 -0
- package/bin/fixtures/benchmarks/core-native/targets/runtime-missing/package.json +4 -0
- package/bin/fixtures/benchmarks/core-native/targets/terraform-locked/.terraform.lock.hcl +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/terraform-locked/main.tf +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/terraform-unlocked-template/.terraform.lock.hcl +3 -0
- package/bin/fixtures/benchmarks/core-native/targets/terraform-unlocked-template/main.tf +7 -0
- package/bin/fixtures/benchmarks/core-native/targets/test-declaration-valid/app.py +2 -0
- package/bin/fixtures/benchmarks/core-native/targets/test-declaration-valid/tests/test_app.py +5 -0
- package/bin/fixtures/benchmarks/core-native/targets/test-path-without-declaration/app.py +2 -0
- package/bin/fixtures/benchmarks/core-native/targets/test-path-without-declaration/tests/test_app.py +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/workflow-malformed/.github/workflows/validate.yml +1 -0
- package/bin/fixtures/benchmarks/core-native/targets/workflow-no-jobs/.github/workflows/empty.yml +9 -0
- package/bin/fixtures/benchmarks/core-native/targets/workflow-risky/.github/workflows/risky.yml +10 -0
- package/bin/fixtures/benchmarks/core-native/targets/workflow-valid/.github/workflows/validate.yml +14 -0
- package/bin/packs/core-foundation.yaml +25 -0
- package/bin/packs/core-native.yaml +59 -0
- package/bin/prc +0 -0
- package/bin/schemas/adapter-execution-v0.1.schema.json +101 -0
- package/bin/schemas/adapter-execution-v0.2.schema.json +128 -0
- package/bin/schemas/adapter-execution.schema.json +145 -0
- package/bin/schemas/adapter-fixture-report.schema.json +59 -0
- package/bin/schemas/adapter-fixture-suite.schema.json +104 -0
- package/bin/schemas/adapter-manifest-v0.1.schema.json +55 -0
- package/bin/schemas/adapter-manifest-v0.2.schema.json +122 -0
- package/bin/schemas/adapter-manifest-v0.3.schema.json +172 -0
- package/bin/schemas/adapter-manifest.schema.json +299 -0
- package/bin/schemas/adapter-message.schema.json +136 -0
- package/bin/schemas/adapter-registry-report.schema.json +13 -0
- package/bin/schemas/adapter-registry.schema.json +47 -0
- package/bin/schemas/agent-execution-v0.1.schema.json +26 -0
- package/bin/schemas/agent-execution.schema.json +26 -0
- package/bin/schemas/agent-failure-v0.1.schema.json +102 -0
- package/bin/schemas/agent-failure.schema.json +102 -0
- package/bin/schemas/agent-output-v0.1.schema.json +36 -0
- package/bin/schemas/agent-output.schema.json +36 -0
- package/bin/schemas/agent-task-v0.1.schema.json +44 -0
- package/bin/schemas/agent-task.schema.json +46 -0
- package/bin/schemas/assertion-catalog.schema.json +69 -0
- package/bin/schemas/benchmark-report.schema.json +94 -0
- package/bin/schemas/benchmark-suite.schema.json +116 -0
- package/bin/schemas/catalog-bundle.schema.json +27 -0
- package/bin/schemas/catalog-manifest.schema.json +23 -0
- package/bin/schemas/checkov-iac-policy-report.schema.json +82 -0
- package/bin/schemas/control-contracts.schema.json +44 -0
- package/bin/schemas/control-review-output.schema.json +51 -0
- package/bin/schemas/doctor.schema.json +53 -0
- package/bin/schemas/evidence-v0.1.schema.json +21 -0
- package/bin/schemas/evidence.schema.json +21 -0
- package/bin/schemas/finding-v0.1.schema.json +70 -0
- package/bin/schemas/finding.schema.json +70 -0
- package/bin/schemas/fix-contract-v0.1.schema.json +35 -0
- package/bin/schemas/fix-contract-v0.2.schema.json +46 -0
- package/bin/schemas/fix-contract-v0.3.schema.json +49 -0
- package/bin/schemas/fix-contract.schema.json +49 -0
- package/bin/schemas/grype-vulnerability-report.schema.json +88 -0
- package/bin/schemas/history.schema.json +37 -0
- package/bin/schemas/invalidation.schema.json +86 -0
- package/bin/schemas/inventory-v0.1.schema.json +42 -0
- package/bin/schemas/inventory-v0.2.schema.json +95 -0
- package/bin/schemas/inventory-v0.3.schema.json +139 -0
- package/bin/schemas/inventory.schema.json +139 -0
- package/bin/schemas/objective-catalog.schema.json +62 -0
- package/bin/schemas/pack-report.schema.json +16 -0
- package/bin/schemas/pack.schema.json +53 -0
- package/bin/schemas/plan-v0.1.schema.json +31 -0
- package/bin/schemas/plan-v0.2.schema.json +32 -0
- package/bin/schemas/plan-v0.3.schema.json +44 -0
- package/bin/schemas/plan-v0.4.schema.json +48 -0
- package/bin/schemas/plan-v0.5.schema.json +49 -0
- package/bin/schemas/plan-v0.6.schema.json +137 -0
- package/bin/schemas/plan.schema.json +137 -0
- package/bin/schemas/profile.schema.json +42 -0
- package/bin/schemas/project-config.schema.json +128 -0
- package/bin/schemas/release-manifest-v0.1.schema.json +86 -0
- package/bin/schemas/release-manifest-v0.2.schema.json +146 -0
- package/bin/schemas/release-manifest-v0.3.schema.json +146 -0
- package/bin/schemas/release-manifest.schema.json +6 -0
- package/bin/schemas/remediation-candidate-v0.1.schema.json +51 -0
- package/bin/schemas/remediation-candidate-v0.2.schema.json +51 -0
- package/bin/schemas/remediation-candidate-v0.3.schema.json +51 -0
- package/bin/schemas/remediation-candidate-v0.4.schema.json +69 -0
- package/bin/schemas/remediation-candidate.schema.json +69 -0
- package/bin/schemas/remediation-run-v0.1.schema.json +69 -0
- package/bin/schemas/remediation-run-v0.2.schema.json +78 -0
- package/bin/schemas/remediation-run-v0.3.schema.json +86 -0
- package/bin/schemas/remediation-run-v0.4.schema.json +86 -0
- package/bin/schemas/remediation-run-v0.5.schema.json +131 -0
- package/bin/schemas/remediation-run-v0.6.schema.json +143 -0
- package/bin/schemas/remediation-run-v0.7.schema.json +160 -0
- package/bin/schemas/remediation-run-v0.8.schema.json +161 -0
- package/bin/schemas/remediation-run.schema.json +161 -0
- package/bin/schemas/risk-exception-verification.schema.json +17 -0
- package/bin/schemas/risk-exception.schema.json +137 -0
- package/bin/schemas/run-result-v0.1.schema.json +54 -0
- package/bin/schemas/run-result-v0.10.schema.json +64 -0
- package/bin/schemas/run-result-v0.11.schema.json +146 -0
- package/bin/schemas/run-result-v0.2.schema.json +60 -0
- package/bin/schemas/run-result-v0.3.schema.json +52 -0
- package/bin/schemas/run-result-v0.4.schema.json +52 -0
- package/bin/schemas/run-result-v0.5.schema.json +60 -0
- package/bin/schemas/run-result-v0.6.schema.json +61 -0
- package/bin/schemas/run-result-v0.7.schema.json +61 -0
- package/bin/schemas/run-result-v0.8.schema.json +61 -0
- package/bin/schemas/run-result-v0.9.schema.json +77 -0
- package/bin/schemas/run-result.schema.json +165 -0
- package/bin/schemas/signature-verification.schema.json +22 -0
- package/bin/schemas/signature.schema.json +18 -0
- package/bin/schemas/state-check-v0.1.schema.json +27 -0
- package/bin/schemas/state-check.schema.json +28 -0
- package/bin/schemas/trust-store.schema.json +50 -0
- package/bin/schemas/verification-execution-v0.1.schema.json +105 -0
- package/bin/schemas/verification-execution.schema.json +105 -0
- package/bin/schemas/version-v0.1.schema.json +27 -0
- package/bin/schemas/version.schema.json +27 -0
- package/manifest.json +9 -0
- package/package.json +28 -0
|
@@ -0,0 +1,330 @@
|
|
|
1
|
+
# Trust, safety, and ecosystems
|
|
2
|
+
|
|
3
|
+
_Phase 14 of 16 in the [complete engineering review](00-overview.md)._
|
|
4
|
+
|
|
5
|
+
Safety-by-design, abuse response, content integrity, authenticity, recommendations, notifications, extensions, plugins, and marketplaces.
|
|
6
|
+
|
|
7
|
+
Assess every control as **Pass**, **Fail**, **Blocked**, or **Not Applicable**. A Pass needs current evidence for the exact product, revision, artifact, configuration, environment, and data state under review.
|
|
8
|
+
|
|
9
|
+
## User-Generated Content, Social Features, and Marketplaces
|
|
10
|
+
|
|
11
|
+
_Consolidated from `quality standards/15-conditional-domains/02-user-generated-content-social-and-marketplaces.md`; 17 non-duplicative controls._
|
|
12
|
+
|
|
13
|
+
### Universal controls
|
|
14
|
+
|
|
15
|
+
- [ ] **USEQ-560779CA** — Acceptable-use, content, conduct, and enforcement policies are defined.
|
|
16
|
+
- [ ] **USEQ-A7D75987** — Users can report prohibited content, harmful conduct, impersonation, fraud, and safety threats.
|
|
17
|
+
- [ ] **USEQ-94462871** — Blocking, muting, audience, privacy, and safety controls work reliably.
|
|
18
|
+
- [ ] **USEQ-6F4DE347** — Moderation queues have owners, severity rules, response objectives, and escalation paths.
|
|
19
|
+
- [ ] **USEQ-9EFA79C0** — Moderator actions are authorized, attributable, reviewable, and audited.
|
|
20
|
+
- [ ] **USEQ-84EE02EE** — Appeals and correction procedures exist where appropriate.
|
|
21
|
+
- [ ] **USEQ-925A28B6** — Spam, bots, scraping, harassment, stalking, impersonation, brigading, and coordinated abuse are addressed.
|
|
22
|
+
- [ ] **USEQ-F0DC21E4** — Uploaded and linked content is scanned and isolated appropriately.
|
|
23
|
+
- [ ] **USEQ-6BE6FEE6** — Illegal-content, copyright, evidence-preservation, lawful-request, and emergency-disclosure procedures are defined.
|
|
24
|
+
- [ ] **USEQ-AF8BAAB3** — Public, private, group, follower, direct-message, and restricted audience controls are clear and enforced server-side.
|
|
25
|
+
- [ ] **USEQ-E0664353** — Deleted or private content does not remain publicly cached, searchable, recommended, or indexed.
|
|
26
|
+
- [ ] **USEQ-5AF9805B** — Search, ranking, notifications, recommendations, and previews do not expose restricted content.
|
|
27
|
+
- [ ] **USEQ-0A61FF1D** — Seller, buyer, provider, creator, or organizer verification is applied where risk requires it.
|
|
28
|
+
- [ ] **USEQ-320189B8** — Fraud, dispute, refund, reputation, review, and trust-and-safety workflows are integrated.
|
|
29
|
+
- [ ] **USEQ-E7BF7973** — Moderation personnel have suitable wellbeing safeguards and restricted data access.
|
|
30
|
+
- [ ] **USEQ-BC1EE838** — Threats to life or safety have an emergency escalation process.
|
|
31
|
+
- [ ] **USEQ-DABCEC8A** — Content-retention and account-deletion behavior is consistent with legal, safety, and privacy requirements.
|
|
32
|
+
|
|
33
|
+
## Email, SMS, Push, and Notifications
|
|
34
|
+
|
|
35
|
+
_Consolidated from `quality standards/15-conditional-domains/03-email-sms-push-and-notifications.md`; 14 non-duplicative controls._
|
|
36
|
+
|
|
37
|
+
### Universal controls
|
|
38
|
+
|
|
39
|
+
- [ ] **USEQ-C773D0E2** — Sender domains, identities, certificates, and provider accounts are controlled.
|
|
40
|
+
- [ ] **USEQ-BE8B8B0B** — Email authentication uses current domain-authentication practices.
|
|
41
|
+
- [ ] **USEQ-9B4FADDD** — Bounce, complaint, rejection, suppression, reputation, and delivery-delay signals are monitored.
|
|
42
|
+
- [ ] **USEQ-C259ED15** — Unsubscribe and preference changes work promptly and are not deceptive.
|
|
43
|
+
- [ ] **USEQ-E68ADD70** — Transactional, security, operational, and marketing messages are classified correctly.
|
|
44
|
+
- [ ] **USEQ-9041D400** — Sensitive information is not exposed unnecessarily in lock-screen content, email previews, SMS, subject lines, or push payloads.
|
|
45
|
+
- [ ] **USEQ-AF1D0C8C** — Reset, verification, invitation, and approval messages cannot be reused or redirected improperly.
|
|
46
|
+
- [ ] **USEQ-30B95EF0** — Retries do not create duplicates, message storms, harassment, or spam.
|
|
47
|
+
- [ ] **USEQ-D7B8731A** — Templates handle localization, escaping, long content, rendering differences, dark mode, plain text, and accessible structure.
|
|
48
|
+
- [ ] **USEQ-AFA6B800** — Provider outage, delay, duplicate delivery, and out-of-order delivery are handled.
|
|
49
|
+
- [ ] **USEQ-BF028AE2** — Frequency and quiet-hour controls prevent harassment and abuse where appropriate.
|
|
50
|
+
- [ ] **USEQ-9B51BA8F** — Phone-number and email-address reassignment risk is considered.
|
|
51
|
+
- [ ] **USEQ-ADF8072F** — Production cannot accidentally use test recipients, and testing cannot accidentally use production recipients.
|
|
52
|
+
- [ ] **USEQ-F56AD22C** — Security notifications are resistant to spoofing and tell users how to verify legitimacy safely.
|
|
53
|
+
|
|
54
|
+
## Search, Ranking, Recommendations, and Personalization
|
|
55
|
+
|
|
56
|
+
_Consolidated from `quality standards/15-conditional-domains/09-search-ranking-recommendations-and-personalization.md`; 13 non-duplicative controls._
|
|
57
|
+
|
|
58
|
+
### Universal controls
|
|
59
|
+
|
|
60
|
+
- [ ] **USEQ-07F09D35** — Search and recommendation inputs, indexes, models, and ranking rules are inventoried.
|
|
61
|
+
- [ ] **USEQ-6D5C3152** — Access control is enforced before indexing, retrieval, ranking, preview, and recommendation.
|
|
62
|
+
- [ ] **USEQ-65B2307E** — Deleted, private, blocked, restricted, or expired content is removed or suppressed promptly.
|
|
63
|
+
- [ ] **USEQ-64BF1EA1** — Query expansion, autocomplete, spelling correction, snippets, and facets do not leak restricted information.
|
|
64
|
+
- [ ] **USEQ-34F34DA1** — Ranking cannot be manipulated trivially through spam, poisoning, coordinated behavior, or hidden metadata.
|
|
65
|
+
- [ ] **USEQ-B3D62C45** — Personalization uses only authorized and disclosed data.
|
|
66
|
+
- [ ] **USEQ-0ED5176E** — Users can understand or control personalization where required.
|
|
67
|
+
- [ ] **USEQ-897DFBBC** — Sensitive traits are not inferred or used without proper review and authorization.
|
|
68
|
+
- [ ] **USEQ-A51E620A** — Fairness, discrimination, safety, diversity, and filter-bubble risks are assessed where material.
|
|
69
|
+
- [ ] **USEQ-387B93A0** — Search and recommendation quality is evaluated across languages, user groups, cold starts, sparse data, and adversarial inputs.
|
|
70
|
+
- [ ] **USEQ-EF56A225** — Caching preserves user, tenant, audience, and permission boundaries.
|
|
71
|
+
- [ ] **USEQ-BD559A2D** — Index lag, model drift, and ranking changes are monitored.
|
|
72
|
+
- [ ] **USEQ-33AC50F2** — A kill switch or rollback exists for harmful ranking or recommendation changes.
|
|
73
|
+
|
|
74
|
+
## Trust, Safety, Content Integrity, and Extension Ecosystems Master Checklist
|
|
75
|
+
|
|
76
|
+
_Consolidated from `gap supplement/04-trust-safety-content-integrity-and-extension-ecosystems.md`; 191 non-duplicative controls._
|
|
77
|
+
|
|
78
|
+
### Expanded gap-closure controls
|
|
79
|
+
|
|
80
|
+
#### Safety-by-design governance
|
|
81
|
+
|
|
82
|
+
- [ ] **USEQ-BD9BA43E** — Apply this checklist whenever users can communicate, publish, transact, discover other users, distribute content, install extensions, delegate capabilities, or materially affect one another.
|
|
83
|
+
- [ ] **USEQ-AEDA607A** — Make user safety a product and governance responsibility rather than assigning it solely to moderation or support after harm occurs.
|
|
84
|
+
- [ ] **USEQ-AFD36B1D** — Assign executive, product, engineering, policy, operations, legal, privacy, security, accessibility, and regional ownership for material safety risks.
|
|
85
|
+
- [ ] **USEQ-596F4B00** — Define the rights, dignity, autonomy, privacy, expression, access, and safety outcomes the product is intended to preserve.
|
|
86
|
+
- [ ] **USEQ-9121E475** — Create a harm taxonomy covering physical, psychological, financial, reputational, privacy, discrimination, exploitation, harassment, fraud, coercion, self-harm, child safety, and societal risks as applicable.
|
|
87
|
+
- [ ] **USEQ-71D94266** — Identify higher-risk users and contexts, including children, survivors, marginalized groups, public figures, workers, sellers, creators, and users under coercion.
|
|
88
|
+
- [ ] **USEQ-E211C089** — Model how product incentives, growth loops, ranking, virality, defaults, anonymity, payments, and friction can increase or reduce harm.
|
|
89
|
+
- [ ] **USEQ-B12D033E** — Include misuse, abuse, coordinated behavior, insider action, compromised accounts, synthetic identities, automation, and cross-platform migration in threat and safety models.
|
|
90
|
+
- [ ] **USEQ-76490994** — Define risk appetite, release blockers, escalation thresholds, emergency actions, and authority to slow or stop growth.
|
|
91
|
+
- [ ] **USEQ-9FB97874** — Fund safety, moderation, investigation, appeals, law-enforcement response where lawful, and victim support proportionately to product reach and risk.
|
|
92
|
+
- [ ] **USEQ-4BE942F0** — Review safety impact before launches, market expansion, new messaging capabilities, recommendation changes, monetization changes, privacy changes, and reduced friction.
|
|
93
|
+
- [ ] **USEQ-C624557C** — Use staged rollout and heightened monitoring for features that change reach, contactability, discoverability, monetization, or user power.
|
|
94
|
+
- [ ] **USEQ-95CED227** — Document safety assumptions and test them with affected users, civil-society expertise, domain specialists, and adversarial research where impact warrants it.
|
|
95
|
+
- [ ] **USEQ-D5D07405** — Publish internal safety objectives and hold leaders accountable for outcome trends, not only content-removal volume.
|
|
96
|
+
|
|
97
|
+
#### Policies, notice, and user expectations
|
|
98
|
+
|
|
99
|
+
- [ ] **USEQ-95E87C5D** — Publish clear, accessible, localized rules for permitted and prohibited content, conduct, commerce, automation, impersonation, and extension behavior.
|
|
100
|
+
- [ ] **USEQ-2A90DDC8** — Make policies specific enough that users, moderators, developers, and reviewers can apply them consistently.
|
|
101
|
+
- [ ] **USEQ-82358F79** — Explain the scope of private, public, encrypted, ephemeral, moderated, and externally visible spaces without making false confidentiality promises.
|
|
102
|
+
- [ ] **USEQ-9ED88D70** — Explain what automated systems, human reviewers, trusted flaggers, merchants, developers, or partners may review and why.
|
|
103
|
+
- [ ] **USEQ-F6F7B3BA** — Provide age, geographic, and product-specific rules where risks and obligations differ.
|
|
104
|
+
- [ ] **USEQ-698F9E31** — Notify users of material policy changes before enforcement where feasible and preserve prior versions.
|
|
105
|
+
- [ ] **USEQ-59123933** — Separate safety rules from promotional language and avoid hiding consequential terms in inaccessible or excessive text.
|
|
106
|
+
- [ ] **USEQ-07E9A6B6** — Give developers and extension publishers explicit technical, privacy, permission, review, update, and enforcement requirements.
|
|
107
|
+
- [ ] **USEQ-1EEF3A16** — State consequences, enforcement ranges, appeal paths, evidence retention, and restoration possibilities.
|
|
108
|
+
- [ ] **USEQ-69D30DCF** — Avoid retroactive punishment for conduct that was permitted unless urgent safety or legal necessity justifies it and the rationale is documented.
|
|
109
|
+
- [ ] **USEQ-6CE2FA9B** — Provide policy examples without creating an exhaustive evasion manual.
|
|
110
|
+
- [ ] **USEQ-5DD0664C** — Ensure policy and product behavior agree; do not promise controls, review, confidentiality, or response times that the system cannot provide.
|
|
111
|
+
|
|
112
|
+
#### User empowerment, consent, and protective controls
|
|
113
|
+
|
|
114
|
+
- [ ] **USEQ-AD777CE0** — Provide understandable privacy, audience, contact, discovery, tagging, messaging, location, recommendation, and data-sharing controls.
|
|
115
|
+
- [ ] **USEQ-A780B514** — Use protective defaults proportionate to age, vulnerability, sensitivity, and expected context.
|
|
116
|
+
- [ ] **USEQ-22F0FF7A** — Allow users to block, mute, restrict, unfollow, leave, remove followers, limit replies, filter keywords, and control contact where relevant.
|
|
117
|
+
- [ ] **USEQ-9D270EFD** — Make safety controls available before, during, and after an interaction rather than only after harm.
|
|
118
|
+
- [ ] **USEQ-A7EF66C3** — Ensure blocking applies consistently across profiles, messages, search, recommendations, notifications, groups, shared content, and alternate identifiers as intended.
|
|
119
|
+
- [ ] **USEQ-486EFD38** — Prevent a blocked or restricted actor from learning unnecessary information through errors, presence, read receipts, recommendations, or indirect notifications.
|
|
120
|
+
- [ ] **USEQ-B65E9725** — Allow users to review and revoke connected applications, sessions, devices, delegates, payment mandates, and extension permissions.
|
|
121
|
+
- [ ] **USEQ-2417A7C7** — Request dangerous permissions at the time of meaningful use and explain the purpose in user language.
|
|
122
|
+
- [ ] **USEQ-D6445268** — Make optional permissions and data collection revocable without forcing account deletion when the core service can continue.
|
|
123
|
+
- [ ] **USEQ-77B28528** — Provide friction, previews, warnings, cooldowns, confirmation, and undo for actions with high abuse or irreversible impact.
|
|
124
|
+
- [ ] **USEQ-29E4B82E** — Allow users to preserve evidence safely before blocking, deleting, or leaving where needed.
|
|
125
|
+
- [ ] **USEQ-7C0C7DE6** — Provide discreet safety exits and account-protection options for users under surveillance or coercion.
|
|
126
|
+
- [ ] **USEQ-ABDF7D26** — Do not expose safety choices publicly when doing so could increase retaliation or stigma.
|
|
127
|
+
- [ ] **USEQ-0CB908CD** — Provide accessible controls and alternatives for users with disabilities, limited literacy, low bandwidth, or constrained devices.
|
|
128
|
+
|
|
129
|
+
#### Reporting, moderation, and case handling
|
|
130
|
+
|
|
131
|
+
- [ ] **USEQ-6092D596** — Provide accessible reporting from the content, account, transaction, message, extension, or behavior being reported.
|
|
132
|
+
- [ ] **USEQ-41AFAEC3** — Allow reporting without requiring the reporter to maintain contact with the reported party.
|
|
133
|
+
- [ ] **USEQ-2EB40D3B** — Offer report categories that support triage while allowing free-text context and urgent-safety signals.
|
|
134
|
+
- [ ] **USEQ-BD179B81** — Acknowledge reports and provide a case reference without exposing protected investigation details.
|
|
135
|
+
- [ ] **USEQ-8A7710F9** — Prioritize cases using severity, imminence, vulnerability, scale, recurrence, virality, illegality, and evidence-loss risk.
|
|
136
|
+
- [ ] **USEQ-FF6C3B4B** — Define service objectives for acknowledgment, triage, emergency escalation, decision, appeal, and restoration by severity.
|
|
137
|
+
- [ ] **USEQ-9BE743D4** — Route credible imminent threats, child-safety risk, self-harm emergencies, financial theft, account compromise, and coordinated abuse to specialized procedures.
|
|
138
|
+
- [ ] **USEQ-36EBFCB9** — Preserve relevant content, metadata, decisions, and chain of custody according to law, policy, privacy, and retention requirements.
|
|
139
|
+
- [ ] **USEQ-5D0E8382** — Protect reporters, moderators, witnesses, and victims from retaliation, doxxing, and unnecessary disclosure.
|
|
140
|
+
- [ ] **USEQ-0750C577** — Use trained reviewers and provide specialized regional, linguistic, cultural, accessibility, legal, and subject-matter support.
|
|
141
|
+
- [ ] **USEQ-FC571D84** — Provide moderators with sufficient context while minimizing unnecessary exposure to personal or traumatic material.
|
|
142
|
+
- [ ] **USEQ-8D51224C** — Use rotation, wellness protections, clinical support, access controls, and workload limits for personnel exposed to harmful content.
|
|
143
|
+
- [ ] **USEQ-4A26124E** — Require consistent decision records including policy basis, evidence, confidence, action, duration, scope, reviewer, and escalation.
|
|
144
|
+
- [ ] **USEQ-1E2471A3** — Use quality assurance, calibration, double review, sampling, and disagreement analysis for consequential decisions.
|
|
145
|
+
- [ ] **USEQ-E9E9307A** — Prevent automated tools from making irreversible high-impact enforcement decisions without the required confidence, safeguards, and human review.
|
|
146
|
+
- [ ] **USEQ-C08DB232** — Provide proportionate actions such as warning, friction, reduced distribution, feature restriction, temporary suspension, removal, preservation, and permanent exclusion.
|
|
147
|
+
- [ ] **USEQ-623ABC6E** — Apply actions across linked accounts or devices only under a documented, privacy-reviewed, error-tolerant policy.
|
|
148
|
+
- [ ] **USEQ-C934C5F6** — Notify affected users with the rule, content or behavior, action, duration, consequences, and appeal route unless doing so would create material risk.
|
|
149
|
+
- [ ] **USEQ-75B5AC01** — Provide accessible, independent, timely appeals with review by someone not solely repeating the original automated decision.
|
|
150
|
+
- [ ] **USEQ-FC548DD3** — Restore content, access, reputation, reach, funds, and associated state when an enforcement error is reversed.
|
|
151
|
+
- [ ] **USEQ-C11B8851** — Track false positives, false negatives, inconsistent decisions, appeal reversals, recurrence, and unresolved backlog.
|
|
152
|
+
|
|
153
|
+
#### Recommendation, amplification, and virality controls
|
|
154
|
+
|
|
155
|
+
- [ ] **USEQ-613FA405** — Treat ranking, recommendation, trending, autocomplete, notifications, resharing, and search as distribution systems with safety responsibilities.
|
|
156
|
+
- [ ] **USEQ-8CB830F6** — Define which safety, quality, provenance, age, sensitivity, and policy signals affect eligibility, ranking, and reach.
|
|
157
|
+
- [ ] **USEQ-AE03B731** — Prevent prohibited or restricted content from re-entering recommendation through copies, edits, alternate encodings, or related accounts.
|
|
158
|
+
- [ ] **USEQ-34281A6E** — Test whether optimization objectives create incentives for outrage, harassment, misinformation, addiction, exploitation, fraud, or unsafe challenges.
|
|
159
|
+
- [ ] **USEQ-1077D020** — Use counter-metrics for harmful exposure, regret, complaints, blocks, hides, rapid exits, appeals, and vulnerable-user impact.
|
|
160
|
+
- [ ] **USEQ-DA6EBB44** — Limit rapid mass distribution for new, untrusted, sensitive, or unusually fast-growing content until risk signals are evaluated where appropriate.
|
|
161
|
+
- [ ] **USEQ-F6C33ECE** — Provide users meaningful control over recommendation topics, sources, personalization, sensitive content, and chronological alternatives where relevant.
|
|
162
|
+
- [ ] **USEQ-435FB22F** — Do not infer or exploit highly sensitive traits for distribution without a lawful, necessary, and user-respecting basis.
|
|
163
|
+
- [ ] **USEQ-F981278F** — Evaluate disparate exposure, suppression, monetization, and error rates across relevant groups and languages.
|
|
164
|
+
- [ ] **USEQ-4676585B** — Ensure downranking and reduced distribution have policy, governance, testing, monitoring, and appeal appropriate to their impact.
|
|
165
|
+
- [ ] **USEQ-075A14AD** — Prevent coordinated manipulation through engagement rings, fake accounts, purchased interactions, adversarial metadata, and automated activity.
|
|
166
|
+
- [ ] **USEQ-06F3E324** — Review recommendation changes through offline evaluation, adversarial testing, limited rollout, causal analysis, and post-launch monitoring.
|
|
167
|
+
- [ ] **USEQ-C776200D** — Provide researchers and auditors appropriate transparency and privacy-preserving access when required or beneficial to safety assurance.
|
|
168
|
+
|
|
169
|
+
#### Identity, impersonation, authenticity, and account integrity
|
|
170
|
+
|
|
171
|
+
- [ ] **USEQ-0C858E3A** — Define when real identity, pseudonymity, anonymity, organization verification, age assurance, or role verification is necessary and proportionate.
|
|
172
|
+
- [ ] **USEQ-7F8BF05A** — Avoid collecting stronger identity evidence than the risk requires.
|
|
173
|
+
- [ ] **USEQ-2AEAE9F2** — Distinguish verified control of an account or organization from endorsement, expertise, factual accuracy, or general trustworthiness.
|
|
174
|
+
- [ ] **USEQ-2BBFCDF2** — Prevent deceptive impersonation of people, organizations, support agents, merchants, public authorities, and automated systems.
|
|
175
|
+
- [ ] **USEQ-33DC094C** — Provide clear disclosure for bots, synthetic personas, delegated operators, and materially automated accounts where users could be misled.
|
|
176
|
+
- [ ] **USEQ-F6D77BAF** — Protect usernames, organization names, custom domains, badges, and profile identifiers from confusing or abusive collision.
|
|
177
|
+
- [ ] **USEQ-F009B337** — Detect account takeover, credential stuffing, session theft, recovery abuse, SIM or email reassignment, and support-channel social engineering.
|
|
178
|
+
- [ ] **USEQ-D805F610** — Use step-up verification and cooling periods for changes to identity, recovery, payout, advertising, administrative, or high-reach settings.
|
|
179
|
+
- [ ] **USEQ-BC52C708** — Notify users of material identity and security changes through independent channels where appropriate.
|
|
180
|
+
- [ ] **USEQ-31D2242A** — Provide recovery paths for compromised accounts without giving attackers an easier route than normal authentication.
|
|
181
|
+
- [ ] **USEQ-C1AD085C** — Preserve evidence and limit further harm during account-takeover investigation.
|
|
182
|
+
- [ ] **USEQ-361A211A** — Allow users to report impersonation even when they do not have an account.
|
|
183
|
+
- [ ] **USEQ-BD3A717B** — Define memorialization, succession, organization transfer, employee departure, and abandoned-account behavior.
|
|
184
|
+
|
|
185
|
+
#### Fraud, spam, bots, and coordinated abuse
|
|
186
|
+
|
|
187
|
+
- [ ] **USEQ-8DE587F8** — Model economic incentives, attacker return, victim loss, platform subsidy, and externalized cost for each abuse class.
|
|
188
|
+
- [ ] **USEQ-41719BE8** — Use layered controls across enrollment, authentication, device, network, behavior, content, transaction, reputation, payout, and recovery.
|
|
189
|
+
- [ ] **USEQ-F2E3DC32** — Bound actions per account, identity, tenant, device, network, payment instrument, destination, and time window using risk-aware limits.
|
|
190
|
+
- [ ] **USEQ-3E29C386** — Detect burst, fan-out, graph, velocity, replay, template, shared-infrastructure, and collusion patterns.
|
|
191
|
+
- [ ] **USEQ-5DEEFFE1** — Prevent rate-limit evasion through alternate endpoints, encodings, identities, tenants, or protocol layers.
|
|
192
|
+
- [ ] **USEQ-EDC9A641** — Use challenges and friction that are accessible, privacy-preserving, and proportionate rather than relying on one CAPTCHA.
|
|
193
|
+
- [ ] **USEQ-19CE9D99** — Separate suspicious activity from proven abuse and avoid irreversible action based on one weak signal.
|
|
194
|
+
- [ ] **USEQ-0D9379C8** — Keep fraud models and rules observable, versioned, tested, monitored for drift, and protected from unauthorized manipulation.
|
|
195
|
+
- [ ] **USEQ-0CC5A940** — Protect high-risk state changes, payouts, refunds, transfers, promotions, invitations, reviews, and messaging from automation abuse.
|
|
196
|
+
- [ ] **USEQ-15AABFBA** — Delay or reserve irreversible value transfer until authoritative risk and settlement signals are available where appropriate.
|
|
197
|
+
- [ ] **USEQ-649D5697** — Reconcile platform records with payment, fulfillment, identity, and provider records to detect hidden losses.
|
|
198
|
+
- [ ] **USEQ-B1FBD274** — Share abuse intelligence internally and with trusted partners under privacy, legal, accuracy, and purpose controls.
|
|
199
|
+
- [ ] **USEQ-6D72C114** — Design containment so blocking one attack does not create widespread denial of service for legitimate users.
|
|
200
|
+
- [ ] **USEQ-1BA3C45A** — Measure attacker adaptation and rotate controls without relying on secrecy as the primary defense.
|
|
201
|
+
|
|
202
|
+
#### Children, vulnerable users, and high-risk interactions
|
|
203
|
+
|
|
204
|
+
- [ ] **USEQ-53975D3E** — Determine whether children are likely users even when the service is not explicitly directed to them.
|
|
205
|
+
- [ ] **USEQ-0BBF963F** — Use age-appropriate defaults for discoverability, contact, location, profiling, advertising, spending, sharing, and public posting.
|
|
206
|
+
- [ ] **USEQ-95346626** — Avoid dark patterns that pressure minors or vulnerable users to disclose data, spend money, maintain streaks, or engage continuously.
|
|
207
|
+
- [ ] **USEQ-BC356E9B** — Limit adult-to-minor contact, grooming patterns, coercive requests, sexualization, and migration to less protected channels where applicable.
|
|
208
|
+
- [ ] **USEQ-FB8D5668** — Provide guardian controls only when lawful and designed not to endanger children in abusive households.
|
|
209
|
+
- [ ] **USEQ-3FC789B0** — Use age assurance proportionate to risk and evaluate privacy, accessibility, bias, circumvention, and exclusion.
|
|
210
|
+
- [ ] **USEQ-4194C938** — Provide child-understandable explanations, reporting, blocking, and help.
|
|
211
|
+
- [ ] **USEQ-FCB00C8A** — Route child-safety incidents to trained teams with strict access, evidence, reporting, and wellness controls.
|
|
212
|
+
- [ ] **USEQ-B0F21CF7** — Protect users seeking help for self-harm, abuse, addiction, financial distress, or violence from exploitation and harmful recommendation loops.
|
|
213
|
+
- [ ] **USEQ-7B563568** — Test safety controls with representative youth and vulnerable-user expertise.
|
|
214
|
+
- [ ] **USEQ-315C17BD** — Avoid public indicators that reveal a user's protected status or safety settings.
|
|
215
|
+
|
|
216
|
+
#### Crisis, emergency, and severe-harm response
|
|
217
|
+
|
|
218
|
+
- [ ] **USEQ-197A27D2** — Define criteria and authority for emergency feature restriction, account freeze, content preservation, distribution reduction, payment hold, or service shutdown.
|
|
219
|
+
- [ ] **USEQ-DC481166** — Maintain current contacts and procedures for emergency services, child-protection channels, payment providers, hosting providers, legal counsel, and trusted experts where applicable.
|
|
220
|
+
- [ ] **USEQ-7545CE12** — Verify jurisdiction, legal basis, identity, scope, urgency, and preservation requirements for emergency requests.
|
|
221
|
+
- [ ] **USEQ-28ED6E96** — Minimize disclosure and record every emergency access or data release.
|
|
222
|
+
- [ ] **USEQ-2C2015DC** — Provide an out-of-band response path when the normal support, identity, or platform systems are compromised.
|
|
223
|
+
- [ ] **USEQ-251F513E** — Exercise scenarios involving credible threats, coordinated violence, mass fraud, viral harmful content, child exploitation, doxxing, extortion, and insider abuse as relevant.
|
|
224
|
+
- [ ] **USEQ-FEB8AB8C** — Coordinate public communication without amplifying harmful material, exposing victims, or prejudicing investigation.
|
|
225
|
+
- [ ] **USEQ-324E1782** — Define when and how affected users are notified after emergency actions.
|
|
226
|
+
- [ ] **USEQ-B38FDE82** — Review emergency actions promptly and reverse overbroad restrictions when safe.
|
|
227
|
+
- [ ] **USEQ-0AE9EFF0** — Conduct post-incident analysis that addresses product incentives, detection gaps, staffing, process, tooling, and governance.
|
|
228
|
+
|
|
229
|
+
#### Content provenance, synthetic media, and authenticity signals
|
|
230
|
+
|
|
231
|
+
- [ ] **USEQ-C6361B6A** — Define which content types and workflows require provenance, origin, edit history, capture context, signer identity, or synthetic-content disclosure.
|
|
232
|
+
- [ ] **USEQ-A3D6E17A** — Use cryptographically bound provenance standards such as C2PA where they meaningfully improve authenticity and ecosystem interoperability.
|
|
233
|
+
- [ ] **USEQ-12397117** — Treat provenance as evidence about claims and history, not proof that content is true, safe, unbiased, or authorized.
|
|
234
|
+
- [ ] **USEQ-87AC1895** — Verify signatures, certificate chains, trust lists, timestamps, asset binding, manifest integrity, revocation, and supported algorithms.
|
|
235
|
+
- [ ] **USEQ-E9A1411C** — Preserve provenance through transcoding, resizing, editing, composition, export, syndication, and archival where technically and legally feasible.
|
|
236
|
+
- [ ] **USEQ-279B0168** — Make provenance loss, invalidity, redaction, and unsupported claims visible rather than presenting a false trusted state.
|
|
237
|
+
- [ ] **USEQ-466DE378** — Protect signing keys, capture credentials, author identities, and provenance services as high-value security assets.
|
|
238
|
+
- [ ] **USEQ-B70CAE6C** — Allow privacy-preserving redaction and selective disclosure without silently rewriting history.
|
|
239
|
+
- [ ] **USEQ-E8CBABAC** — Provide accessible human-readable explanations of provenance and avoid binary trusted/untrusted labels that overstate confidence.
|
|
240
|
+
- [ ] **USEQ-A48CB2BE** — Record automated generation, material editing, model or tool identity, source assets, and responsible publisher when required by policy or risk.
|
|
241
|
+
- [ ] **USEQ-175ACA22** — Use visible labels, watermarks, metadata, detection, and user education as complementary controls; do not rely on one mechanism as perfect detection.
|
|
242
|
+
- [ ] **USEQ-59C5F9CA** — Evaluate provenance spoofing, stripping, laundering, replay, key compromise, trust-list abuse, and misleading authentic-but-harmful content.
|
|
243
|
+
- [ ] **USEQ-9C34ECD6** — Monitor ecosystem support and maintain graceful behavior when receiving unknown or newer provenance formats.
|
|
244
|
+
|
|
245
|
+
#### Extension, plugin, app, and integration ecosystems
|
|
246
|
+
|
|
247
|
+
- [ ] **USEQ-BF82CD25** — Apply a formal intake, review, publication, update, monitoring, enforcement, and retirement lifecycle to third-party extensions and integrations.
|
|
248
|
+
- [ ] **USEQ-0B382DF6** — Require an accurate description of functionality, data access, remote services, permissions, monetization, ownership, support, and security practices.
|
|
249
|
+
- [ ] **USEQ-ABE691EB** — Require only the minimum permissions and allow optional permissions to be requested at meaningful use time where supported.
|
|
250
|
+
- [ ] **USEQ-2900DB5A** — Make permission prompts specific, understandable, attributable, and revisitable.
|
|
251
|
+
- [ ] **USEQ-E6B9618B** — Prevent extensions from loading unreviewed remote executable code or silently changing behavior outside the approved update channel.
|
|
252
|
+
- [ ] **USEQ-9EF29D9E** — Require reviewable source or reproducible correspondence between submitted source and distributed artifact for high-risk ecosystems.
|
|
253
|
+
- [ ] **USEQ-EC3D9D3D** — Scan dependencies, secrets, malware, obfuscation, suspicious behavior, policy violations, and known vulnerabilities.
|
|
254
|
+
- [ ] **USEQ-5CC601B2** — Restrict dynamic evaluation, native execution, privileged APIs, cross-origin access, filesystem access, identity access, and payment access according to risk.
|
|
255
|
+
- [ ] **USEQ-D2594826** — Sandbox extension execution and isolate storage, network, UI, processes, credentials, and tenant context where practical.
|
|
256
|
+
- [ ] **USEQ-9BBB4EEA** — Prevent an extension from weakening host security headers, transport security, authentication, authorization, privacy, accessibility, or audit controls.
|
|
257
|
+
- [ ] **USEQ-632E8E55** — Require encrypted transport and authenticated endpoints for extension data exchange.
|
|
258
|
+
- [ ] **USEQ-5EDDE5B2** — Require transparent data collection, purpose, retention, sharing, sale, consent, and deletion behavior.
|
|
259
|
+
- [ ] **USEQ-48EB755B** — Test extension performance, memory, battery, startup, stability, offline behavior, accessibility, localization, and failure containment.
|
|
260
|
+
- [ ] **USEQ-3452812F** — Prevent one faulty or malicious extension from crashing, blocking, corrupting, or exfiltrating the host or other extensions.
|
|
261
|
+
- [ ] **USEQ-7A7CA22D** — Use signed packages and a secure update framework resistant to rollback, freeze, mix-and-match, repository compromise, and signing-key compromise.
|
|
262
|
+
- [ ] **USEQ-245DA35C** — Support staged rollout, compatibility checks, rollback or disablement, revocation, and emergency blocklisting.
|
|
263
|
+
- [ ] **USEQ-96481324** — Make extension identity, publisher changes, ownership transfers, and signing-key changes reviewable and visible.
|
|
264
|
+
- [ ] **USEQ-9DB20BBB** — Require updates that add permissions, data use, remote services, or materially different behavior to receive renewed review and user notice.
|
|
265
|
+
- [ ] **USEQ-724B59B6** — Monitor abuse reports, crash rates, permission use, network destinations, update anomalies, dormant takeover, and publisher compromise.
|
|
266
|
+
- [ ] **USEQ-55B8A0A8** — Provide users a clear inventory, enable/disable control, permission review, update history, and removal path.
|
|
267
|
+
- [ ] **USEQ-374B203B** — Remove credentials, data access, webhooks, tokens, stored data, background jobs, and delegated rights when an integration is removed.
|
|
268
|
+
- [ ] **USEQ-575DA746** — Define compatibility and deprecation policy for host APIs without forcing insecure legacy support indefinitely.
|
|
269
|
+
- [ ] **USEQ-130FF33D** — Provide an appeal process for developers while prioritizing user safety during credible compromise.
|
|
270
|
+
|
|
271
|
+
#### Ecosystem and marketplace governance
|
|
272
|
+
|
|
273
|
+
- [ ] **USEQ-A9C693F2** — Verify merchants, developers, advertisers, creators, and high-reach accounts proportionately to their ability to cause harm.
|
|
274
|
+
- [ ] **USEQ-3F7F7E38** — Separate platform endorsement, verification, popularity, ranking, and paid placement visually and semantically.
|
|
275
|
+
- [ ] **USEQ-5242F580** — Disclose commissions, fees, sponsorship, ranking influence, and platform conflicts that materially affect user choice.
|
|
276
|
+
- [ ] **USEQ-9F589E1F** — Prevent review manipulation, fake testimonials, retaliatory reviews, review gating, and undisclosed incentives.
|
|
277
|
+
- [ ] **USEQ-7750BA91** — Protect sellers, creators, and developers from arbitrary enforcement through published rules, notice, evidence, appeal, and restoration.
|
|
278
|
+
- [ ] **USEQ-1AA1AED9** — Prevent marketplace design from pushing risk, support, refunds, tax, safety, or legal obligations onto users without clarity.
|
|
279
|
+
- [ ] **USEQ-941BFF73** — Define responsibility for product safety, prohibited goods, intellectual property, counterfeit claims, fulfillment, refunds, and disputes.
|
|
280
|
+
- [ ] **USEQ-6CD3ED9A** — Monitor dormant account or package takeover, ownership transfers, sudden behavior changes, and supply-chain compromise.
|
|
281
|
+
- [ ] **USEQ-DF8621BD** — Apply progressive trust and limits rather than granting full reach, payouts, or permissions immediately to unproven participants.
|
|
282
|
+
- [ ] **USEQ-A847268E** — Provide transparent complaint and dispute resolution with evidence and deadlines.
|
|
283
|
+
- [ ] **USEQ-7ADC4406** — Measure ecosystem health using user harm, fraud loss, quality, diversity, concentration, developer sustainability, false enforcement, and support—not gross volume alone.
|
|
284
|
+
|
|
285
|
+
#### Transparency, audit, and continuous improvement
|
|
286
|
+
|
|
287
|
+
- [ ] **USEQ-0164140D** — Publish meaningful aggregate information about policies, reports, enforcement, appeals, automation, severe harms, and response performance where appropriate.
|
|
288
|
+
- [ ] **USEQ-8C2EE771** — Explain material recommendation, verification, provenance, and enforcement systems at a level users and oversight bodies can understand.
|
|
289
|
+
- [ ] **USEQ-99F86F23** — Disclose the limits and known error modes of automated moderation, age assurance, identity, fraud, and provenance systems.
|
|
290
|
+
- [ ] **USEQ-DF46D365** — Protect transparency reports against privacy leakage, reidentification, security evasion, and misleading aggregation.
|
|
291
|
+
- [ ] **USEQ-EB1EF776** — Provide independent audit, researcher access, regulator access, or trusted oversight where risk or obligation warrants it.
|
|
292
|
+
- [ ] **USEQ-AA903343** — Retain model, rule, policy, reviewer, evidence, and version information needed to reconstruct consequential decisions.
|
|
293
|
+
- [ ] **USEQ-2140FACB** — Track harm prevalence and exposure, not only the number of items removed.
|
|
294
|
+
- [ ] **USEQ-FB9F9E37** — Measure time to detection, interruption, victim support, recovery, appeal, and recurrence prevention.
|
|
295
|
+
- [ ] **USEQ-CCCAA8A8** — Review false-positive and false-negative impacts across languages, regions, disabilities, ages, and affected groups.
|
|
296
|
+
- [ ] **USEQ-DF0CB7C2** — Use red-team, tabletop, abuse simulation, user research, and incident learning to discover controls that ordinary testing misses.
|
|
297
|
+
- [ ] **USEQ-E3F9DBC4** — Convert recurring abuse into safer defaults, reduced capability, stronger boundaries, better education, and redesigned incentives.
|
|
298
|
+
- [ ] **USEQ-4C29738F** — Review this checklist after major incidents, market expansion, policy changes, new content formats, new extension capabilities, or attacker adaptation.
|
|
299
|
+
|
|
300
|
+
#### Trust-and-safety release blockers
|
|
301
|
+
|
|
302
|
+
- [ ] **USEQ-9B250F50** — Do not launch a high-risk interaction surface without reporting, blocking, escalation, evidence, enforcement, and appeal paths.
|
|
303
|
+
- [ ] **USEQ-69245CE0** — Do not launch when severe-harm reports cannot reach a qualified responder within the required objective.
|
|
304
|
+
- [ ] **USEQ-97EA05F5** — Do not launch a recommendation or virality change when harmful-exposure and abuse effects are unmeasured and uncontrolled.
|
|
305
|
+
- [ ] **USEQ-FE34F2BA** — Do not grant broad extension permissions, remote code execution, or privileged host access without review, containment, transparency, and revocation.
|
|
306
|
+
- [ ] **USEQ-3FF9D040** — Do not distribute updates whose source, signer, version, and authorized update path cannot be verified.
|
|
307
|
+
- [ ] **USEQ-0D13B7DC** — Do not present provenance, verification, or identity badges in a way that falsely implies truth, endorsement, expertise, or safety.
|
|
308
|
+
- [ ] **USEQ-307DFDE0** — Do not collect identity or age evidence beyond demonstrated necessity and protection capability.
|
|
309
|
+
- [ ] **USEQ-04AA676C** — Do not make irreversible enforcement or financial decisions from one opaque automated signal without required review and recovery.
|
|
310
|
+
- [ ] **USEQ-01689474** — Do not suppress known severe-harm trends to protect growth, engagement, reputation, or revenue metrics.
|
|
311
|
+
- [ ] **USEQ-9F34570B** — Do not accept a safety exception without an explicit harm analysis, protective alternative, monitoring, owner, remediation date, and expiry.
|
|
312
|
+
|
|
313
|
+
## Standards and source references
|
|
314
|
+
|
|
315
|
+
- [ISO/IEC 25010:2023 — Product quality model](https://www.iso.org/standard/78176.html)
|
|
316
|
+
- [NIST Cybersecurity Framework 2.0](https://www.nist.gov/cyberframework)
|
|
317
|
+
- [ISO/IEC 27701:2025 — Privacy information management systems](https://www.iso.org/standard/85819.html)
|
|
318
|
+
- [ISO/IEC 42001:2023 — AI management systems](https://www.iso.org/standard/81230.html)
|
|
319
|
+
- [ISO/IEC 23894:2023 — AI risk management](https://www.iso.org/standard/77304.html)
|
|
320
|
+
- [eSafety Safety by Design](https://www.esafety.gov.au/industry/safety-by-design)
|
|
321
|
+
- [C2PA Specifications 2.4](https://spec.c2pa.org/specifications/specifications/2.4/index.html)
|
|
322
|
+
- [C2PA Security Considerations](https://spec.c2pa.org/specifications/specifications/2.4/security/Security_Considerations.html)
|
|
323
|
+
- [Mozilla Add-on Policies](https://extensionworkshop.com/documentation/publish/add-on-policies/)
|
|
324
|
+
- [Mozilla permission guidance](https://extensionworkshop.com/documentation/develop/request-the-right-permissions/)
|
|
325
|
+
- [The Update Framework](https://theupdateframework.io/)
|
|
326
|
+
- [NIST AI 100-4 — Reducing Risks Posed by Synthetic Content](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-4.pdf)
|
|
327
|
+
|
|
328
|
+
---
|
|
329
|
+
|
|
330
|
+
[Previous phase](13-documentation-and-knowledge.md) · [Next: Phase 15: AI, ML, and AI-assisted development](15-ai-ml-and-ai-assisted-development.md)
|