security_mechanism stringclasses 3
values | verification_label stringclasses 2
values | claim_text stringclasses 3
values | source_url null | evidence_text stringclasses 3
values | verification_rationale stringclasses 3
values |
|---|---|---|---|---|---|
Cross-Origin Resource Sharing (CORS); credentialed requests | 反驳 | A server can authorize credentialed cross-origin requests from any origin by returning Access-Control-Allow-Origin: * together with Access-Control-Allow-Credentials: true. | null | When a response to a credentialed request has Access-Control-Allow-Credentials set to true, the Access-Control-Allow-Origin value must identify the requesting origin; the wildcard value is not permitted for this response. | The evidence says that a credentialed response must specify the requesting origin and cannot use the wildcard value. It therefore contradicts the claim that the wildcard can authorize credentialed requests from any origin. |
Content Security Policy (CSP); default-src fallback | 支持 | If a Content Security Policy omits script-src, default-src can act as the fallback directive for external script fetches. | null | The default-src directive serves as a fallback for fetch directives that are not explicitly set. If script-src is not specified, default-src supplies the policy for script resource requests. | The evidence explicitly identifies default-src as the fallback for unspecified fetch directives and names script resource requests when script-src is absent. This supports the claim about external script fetches. |
Cookies; SameSite; Secure | 反驳 | A cookie configured with SameSite=None can be set without the Secure attribute and still be accepted for cross-site use. | null | Cookies that specify SameSite=None must also specify Secure. User agents reject cookies with SameSite=None that do not include Secure. | The evidence states that a SameSite=None cookie must include Secure and that user agents reject it otherwise. This contradicts the claim that such a cookie can be set without Secure and accepted for cross-site use. |
Web Platform Security Behavior Fact Verification Dataset
This dataset focuses on security behavior in browsers, Web protocols, and common application frameworks, covering mechanisms such as cookies, Cross-Origin Resource Sharing (CORS), and Content Security Policy (CSP). Each record links a technical claim to evidence from official documentation or other web text, and includes a verification label, rationale, and security mechanism category. The data supports fact-verification model training and evaluation, Web application security analysis, technical knowledge validation, and evidence-tracing research.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| claim_text | string | A factual claim about security behavior in a browser, Web protocol, or application framework that requires verification. |
| source_url | string | The original URL of the webpage containing the evidence. |
| evidence_text | string | An excerpt from official documentation or other web text used to verify the claim. |
| security_mechanism | string | The Web security mechanism addressed by the claim, such as cookies, Cross-Origin Resource Sharing, or Content Security Policy. |
| verification_label | string | The judgment of whether the claim is supported by the evidence. |
| verification_rationale | string | An explanation of how the evidence relates to the claim and supports the verification judgment. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- -