snowchive-meta/data/xks-workflows-2009/metadata.json
2026-11-19 04:39:11 +02:00

53 lines
5.7 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

{
"title": "XKEYSCORE Workflows 2009",
"type": "REPORTED",
"description": "A 2009 XKeyscore training presentation on Workflows — standing automated queries that run on a schedule against XKeyscore's rolling buffer — walking analysts through the Workflow Central request wizard to build recurring searches with follow-on actions like email alerts, session downloads to Agility, MAILORDER forwarding and SQL reports, with login banners showing the Menwith Hill Station Human Rights Act and Sensitive Targeting Approval compliance regime.",
"long_description": "This is a SECRET//COMINT//REL TO USA, AUS, CAN, GBR, NZL XKeyscore training presentation dated 5 March 2009 on Workflows. It teaches analysts how to create and manage workflows — automated standing queries that run on a schedule — through the Workflow Central request wizard.\n\nWorkflows automate any XKeyscore search type as either one-time or standing queries, offering the same functionality as ad hoc searches but running on a schedule. They can be configured to run once over a set datetime range, or recurringly every 1, 2, 3, 4, 6, 8, 12 or 24 hours with a configurable start offset. The rationale for workflows includes the fact that XKeyscore holds only a rolling buffer of data (so standing queries capture data before it ages off), repetitive SIGDEV queries, fingerprint and AppID testing, and avoiding long query times during peak periods. Anyone can submit a workflow; each has a single owner (though multiple users can be notified), and results appear only in the owner's My Results view. Follow-on actions include email alerts, session downloads, MAILORDER forwarding, and MySQL reports.\n\nThe bulk of the presentation is a step-by-step walkthrough of the request wizard using an example workflow named \"Find_my_appid\" (justified as \"Testing appid signature\"), which searches the Full Log for traffic from IP 1.2.3.4 to port 80 matching the AppID fingerprint search/google*, running every 6 hours starting at 5:00 EST. The walkthrough covers search type selection, basic information entry (with required unique query names and justifications), search field addition (with detailed explanation of Boolean AND/OR logic — values ANDed by default, ORed via the Multiple Field Search tab or \"OR\" between values), the group-by option, database selection, and the various follow-on actions. The follow-on action screens detail email alerts (comma-delimited addresses, sent only if the workflow has results via the ROWR \"Return Only With Results\" flag), SQL reports (CSV or HTML output from a valid SQL statement against the output table, with an example grouping casenotations by SIGAD), and download sessions (including a \"Send To Agility\" option and MAILORDER trigraph routing).\n\nThe approved workflow screen reveals the underlying XML job structure, including — notably — an xks_password field containing a hashed value (18837b706121a0ca), the interval/offset scheduling, the SQL where-clause with fm_ip, to_ap and fingerprint fields, and the routing to the analyst's personal query database (xks-jychan:q0). The common mistakes section provides troubleshooting guidance on Boolean logic pitfalls (From/To IP with the same value, the behaviour of negation where \"!a\" defeats \"a\" but not \"b\", requiring all defeated values to be ANDed), SIGAD/site selection efficiency, and SQL validity.\n\nThe login banners throughout carry the significant compliance apparatus seen in other Menwith Hill-associated XKeyscore documents: \"This system is audited for USSID 18 and Human Rights Act compliance,\" and the notice describing the Sensitive Targeting Approval (STA) requirement before querying terms specific to a UK, British Dependent Territory or Second Party person or location, with legal guidance available from the HRA Compliance Officer at Menwith Hill Station. The database selection screen showing AUS sites, F6 sites and NZ sites confirms the multi-national, Five Eyes-wide reach of the workflow system.\n\nThe document is significant as detailed documentation of how analysts operationalised persistent, automated surveillance through XKeyscore — turning one-off queries into continuous monitoring that automatically captured, alerted on, downloaded and forwarded matching traffic before it aged out of the buffer. The Human Rights Act and STA compliance framework, the reference to Menwith Hill Station, and the AUS/F6/NZ site options together confirm the document reflects a GCHQ-associated deployment operating under UK legal oversight alongside NSA.",
"tags": [
"workflow",
"automated query",
"rolling buffer",
"Menwith Hill",
"MHS",
"query database"
],
"document": {
"creator": "NSA",
"date_created": "2009-03-05",
"classification": [
"SECRET",
"COMINT"
],
"dissemination": [
"REL TO USA, AUS, CAN, GBR, NZL"
],
"banner": "SECRET//COMINT//REL TO USA, AUS, CAN, GBR, NZL",
"genre": "slides",
"programs": [
"XKEYSCORE",
"MAILORDER",
"AGILITY"
],
"countries": [],
"people": []
},
"publication": [
{
"publisher": "The Intercept",
"date_published": "2015-07-01",
"title": "XKEYSCORE: NSA’s Google for the World’s Private Communications",
"link": "https://theintercept.com/2015/07/01/nsas-google-worlds-private-communications/",
"reporters": [
"Marquis-Boire, Morgan",
"Greenwald, Glenn",
"Lee, Micah"
],
"contributors": [],
"doc_source": "https://theintercept.com/document/2015/07/01/xks-workflows-2009/",
"doc_url": "https://s3.documentcloud.org/documents/2157515/xks-workflows-2009.pdf"
}
],
"aka_id": [],
"pdf_sha256": "4289f684941779eb3d4275bab8c81548cf3342c32e14738f8c5d615de2f33041",
"pages": 24
}