first commit
This commit is contained in:
commit
0d90363116
6510 changed files with 679146 additions and 0 deletions
177
data/architecture-risk-2012/architecture-risk-2012.md
Normal file
177
data/architecture-risk-2012/architecture-risk-2012.md
Normal file
|
|
@ -0,0 +1,177 @@
|
|||
TOP SECRET STRAP1
|
||||
|
||||
Report on Architectural Risk 2012 - Summary
|
||||
|
||||
12/3/2012
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
Introduction
|
||||
|
||||
1. The 2011 Corporate Technology Risk identified our solution architecture as being one of the contributors to the High risk rating. In recent years a strong focus on delivery has resulted in an under investment in architecture. This will eventually have an impact on our ability to deliver.
|
||||
|
||||
2. The December board meeting were concerned that investment decisions being made in the 2012/13 portfolio build could be non-optimal if architecture considerations were not taken into account and asked the following question:
|
||||
|
||||
"Given our changes in mission and changes in the external environment (Cyber defence, offensive cyber, increased partnering, increased data volumes, etc) which parts of our architecture are under most strain and so carry the most risk to this year's investment “
|
||||
|
||||
3. Part of the new DCTO role is to define a technology vision and then champion improvements to the solution architecture at portfolio build time. However, it will take time to construct that vision. Therefore in the interim a broad brush approach has been taken in order to allow some immediate advice to be given to the portfolio.
|
||||
|
||||
4. We have a defined a number of high level change drivers on the architecture (Annex 1). These are changes in either our mission, ways of doing business or external technology which are relatively recent and were not taken into account when our current solution architecture was built. We have also represented our current solution architecture as a number of high level elements. We then assessed each change driver against the current solution architecture and identified those architectural elements most stressed by the drivers (Annex 3 and Annex 4).
|
||||
|
||||
5. This has been done in a short period of time with only limited amounts of effort. There are therefore a number of caveats that need to be made:
|
||||
* This is a broad brush, high level analysis.
|
||||
* Whilst we have consulted as widely as possible, we have inevitably not managed to consult everyone we would have liked to have involved
|
||||
* We have restricted ourselves to the infrastructure and application layers (and so not explicitly considered the business layer)
|
||||
* We are not attempting to define the "to-be" solution architecture. Instead we have concentrated on identifying risks with the current architecture
|
||||
|
||||
2 of 6
|
||||
This information is exempt from disclosure under the Freedom of Information Act 2000 and may be subject to exemption under other UK information legislation. Refer disclosure requests to GCHQ o[REDACTED]
|
||||
TOP SECRET STRAP1
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
Recommendations
|
||||
|
||||
6. This high-level architectural analysis has highlighted parts of the solution architecture which needs immediate attention. There are currently line items in the unconstrained portfolio build which will help address the three main concerns. It is recommended that these line items are prioritised in the filter and twist phase.
|
||||
|
||||
* Big Data. We need to develop an end-end big data strategy which covers expected data growth, tradecraft, QFD architecture, cloud architecture, Black Hole, the role of streaming analytics and the proposed new data centre. A series of experiments should be carried out between TA, TDB innovation, ICTR and SD to de-risk some of the possible solutions.
|
||||
* Integrated Analytics Framework. We need to converge to a small number of analytics frameworks for use across our multiple missions which support the rapid deployment of experimental analytics tools and provide the APIs required for fused analytics.
|
||||
* Security Services. We need to provide an end to end and cohesive uplift to the capabilities used to support assured information sharing within and across our enterprise boundaries, with support to the Information Assurance agenda, ensuring the appropriate accessibility, releasibility and traceability.
|
||||
* Vision and Strategy. The coherence we need in order to deliver against the drivers needs investment into the development of end to end technical vision and supporting technology strategies, supporting the business needs. The current "redness" in Annex 3 demonstrates that there are some fundamental changes required to the architecture. Whilst the first three recommendations will address some of the more urgent symptoms we need to also invest in addressing the underlying causes.
|
||||
|
||||
7. NSA are already some way down the path of instantiating their new architecture. Their "2017 Vision: the Future of NSA IT" has a small number of principles: smart data; virtualization and mobility. As we construct our equivalent vision we need, as a minimum, to be interoperable with NSA's new architecture. We should also look to take as much advantage as makes sense of NSA's specific implementations.
|
||||
|
||||
8. Finally, please note this report was created over a short period of time with only limited amounts of effort. There is a need to establish an appropriate framework that allows a more considered view to be presented as input to future portfolio builds.
|
||||
|
||||
3 of 6
|
||||
This information is exempt from disclosure under the Freedom of Information Act 2000 and may be subject to exemption under other UK information legislation. Refer disclosure requests to GCHQ o[REDACTED]
|
||||
TOP SECRET STRAP1
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
Annex 1: Change Drivers
|
||||
|
||||
1. Size of access => vastly increased data volumes
|
||||
2. Increase in number and type of customers (wider government, industry, third parties) i.e. our consumers
|
||||
- And more points where are customers interact with us (not just EP)
|
||||
3. Increase in number and type of partners (SIA, MOD, industry, 3rd parties) i.e. our providers
|
||||
4. NSA/US IT efficiencies
|
||||
- Rationalisation of systems
|
||||
- More integrated US intelligence community
|
||||
5. Increased size of internet connectivity
|
||||
- One way, two way, covert
|
||||
- More reliance on open source obtained from internet
|
||||
6. Increased presence/activity on internet
|
||||
- Scaling up of CNE (more implants, more supporting infrastructure etc)
|
||||
7. Speed of change of internet services leading to:
|
||||
- Lots of capability in experiment space
|
||||
- Analyst task becomes harder
|
||||
- Analyst - developer model
|
||||
- More types of data
|
||||
- Need for more innovation (which needs open interfaces)
|
||||
8. Our wider integrated mission (Sigint, Domestic, IA, Cyber Defence, Effects)
|
||||
9. Increased need to take action in near real time
|
||||
10. Increased emphasis on GCHQ's Reputation (IA exemplar, Legal, Business Continuity)
|
||||
11. Major Technology trends:
|
||||
- Mobile broadband and devices
|
||||
- Spread of SSL/VPNs/ubiquitous encryption
|
||||
12. Mobility of our users
|
||||
13. Less money (Finite/shrinking resources)
|
||||
- To build systems
|
||||
- Support systems (power, space, cooling)
|
||||
14. More use of industry to build our capability
|
||||
15. Increased amount of difficult work (in scale & complexity) placing more demand on our limited numbers of highly skilled people
|
||||
16. Volatility of target networks
|
||||
|
||||
4 of 6
|
||||
This information is exempt from disclosure under the Freedom of Information Act 2000 and may be subject to exemption under other UK information legislation. Refer disclosure requests to GCHQ on [REDACTED]
|
||||
TOP SECRET STRAP1
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
Annex 3: Mapping of Drivers to Architecture Elements
|
||||
|
||||
Technology Drivers
|
||||
|
||||
1. Scale of data volume and ingest rate
|
||||
2. Bring compute to data rather than data to compute
|
||||
3. Ability to ask "new questions" of old data
|
||||
4. Reduce time from data acquisition to mission…
|
||||
5. Increase use of structured and semi-structured data…
|
||||
6. Move away from application-centric to data-centric…
|
||||
7. Move to commodity hardware…
|
||||
GCHQ Drivers
|
||||
Wider Drivers
|
||||
Historic & Future
|
||||
Cost Model
|
||||
Depot
|
||||
Data
|
||||
Processing
|
||||
Storage
|
||||
Security
|
||||
End-User
|
||||
Info-centric
|
||||
Services
|
||||
Network
|
||||
Platform
|
||||
Hosting
|
||||
Management
|
||||
Auto Services
|
||||
Business Process
|
||||
Billing
|
||||
Partner
|
||||
|
||||
5 of 6
|
||||
This information is exempt from disclosure under the Freedom of Information Act 2000 and may be subject to exemption under other UK information legislation. Refer disclosure requests to GCHQ o[REDACTED]
|
||||
TOP SECRET STRAP1
|
||||
|
||||
TOP SECRET STRAP1
|
||||
|
||||
Annex 4: Summary of RAG Status of each Architectural Element
|
||||
|
||||
Business
|
||||
* Collection Access
|
||||
* Process & Store
|
||||
* Analyse & Store
|
||||
* Report & Store
|
||||
* Effects Access
|
||||
* Cause Effect
|
||||
* Manage the Mission
|
||||
* Assess Options
|
||||
* Manage Requirements
|
||||
* Manage Customer Relations
|
||||
* Evaluate Mission
|
||||
* Capability Development
|
||||
|
||||
Applications
|
||||
* Access
|
||||
* Processing
|
||||
* Storage
|
||||
* Analysis
|
||||
* Reporting/Response
|
||||
* Launch Platform
|
||||
* Target Env Lab
|
||||
* Mission Management
|
||||
* Mission Knowledge
|
||||
IC
|
||||
|
||||
Infrastructure
|
||||
* Audit/Accounting
|
||||
* Security Services
|
||||
* Storage
|
||||
* Active Content Handling
|
||||
* Desktop
|
||||
* Facilities
|
||||
* Information Transfer Service
|
||||
* Networks
|
||||
* Gateways
|
||||
* Hosting
|
||||
* HEC
|
||||
* IT Management
|
||||
* Info sharing/collaboration
|
||||
|
||||
6 of 6
|
||||
This information is exempt from disclosure under the Freedom of Information Act 2000 and may be subject to exemption under other UK information legislation. Refer disclosure requests to GCHQ on [REDACTED]
|
||||
TOP SECRET STRAP1
|
||||
67
data/architecture-risk-2012/metadata.json
Normal file
67
data/architecture-risk-2012/metadata.json
Normal file
|
|
@ -0,0 +1,67 @@
|
|||
{
|
||||
"title": "Report on Architectural Risk 2012 - Summary",
|
||||
"type": "REPORTED",
|
||||
"description": "This 2012 GCHQ report identifies that a historical under-investment in IT architecture has created significant risk, especially with new challenges like massive data growth, cyber defense, and increased partnering. The document recommends immediate, prioritized investment in big data strategies, integrated analytics frameworks, and security services to address the strain on the system.",
|
||||
"long_description": "This 2012 GCHQ report is a high-level risk assessment of the agency's solution architecture, prompted by board-level concerns that a historical under-investment in architecture posed a threat to future mission delivery. The analysis was conducted rapidly to inform the 2012/13 investment portfolio, identifying which architectural components were under the most strain from new \"change drivers\" like massive data volume increases, cyber defense missions, and increased partnering. The document deliberately avoids defining a future architecture, instead focusing on identifying immediate risks within the existing infrastructure and application layers to guide prioritization of funding.\n\nThe report's key recommendations are to immediately prioritize investment in three main areas: developing an end-to-end \"Big Data\" strategy to handle data growth; converging on an \"Integrated Analytics Framework\" to speed up tool deployment; and implementing a cohesive uplift to \"Security Services\" for better information sharing. It strongly advises that GCHQ's long-term vision must be interoperable with the NSA's new architecture, which was already in development, and that dedicated funding is needed to address the underlying architectural issues, not just the immediate symptoms.",
|
||||
"tags": [
|
||||
"risk assessment",
|
||||
"Solution Architecture",
|
||||
"IT strategy",
|
||||
"Technology Vision",
|
||||
"investment",
|
||||
"portfolio build",
|
||||
"change drivers",
|
||||
"mission creep",
|
||||
"partnership",
|
||||
"big data",
|
||||
"data volume",
|
||||
"integrated analytics framework",
|
||||
"data fusion",
|
||||
"Security Service",
|
||||
"Information Assurance",
|
||||
"interoperability",
|
||||
"2017 Vision",
|
||||
"smart data",
|
||||
"virtualization",
|
||||
"mobility",
|
||||
"cloud computing",
|
||||
"streaming analytics",
|
||||
"BLACK HOLE",
|
||||
"Computer Network Exploitation",
|
||||
"QFD",
|
||||
"funding",
|
||||
"financial problems"
|
||||
],
|
||||
"document": {
|
||||
"creator": "GCHQ",
|
||||
"date_created": "2012-12-03",
|
||||
"classification": [
|
||||
"TOP SECRET",
|
||||
"STRAP 1"
|
||||
],
|
||||
"dissemination": [],
|
||||
"banner": "TOP SECRET STRAP1",
|
||||
"genre": "report",
|
||||
"programs": [
|
||||
"BLACKHOLE"
|
||||
],
|
||||
"countries": [],
|
||||
"people": []
|
||||
},
|
||||
"publication": [
|
||||
{
|
||||
"publisher": "The Intercept",
|
||||
"date_published": "2015-09-25",
|
||||
"title": "Profiled: From Radio to Porn, British Spies Track Web Users' Online Identities",
|
||||
"link": "https://theintercept.com/2015/09/25/gchq-radio-porn-spies-track-web-users-online-identities/",
|
||||
"reporters": [
|
||||
"Gallagher, Ryan"
|
||||
],
|
||||
"contributors": [],
|
||||
"doc_source": "https://theintercept.com/document/2015/09/25/architecture-risk-2012/",
|
||||
"doc_url": "https://s3.documentcloud.org/documents/2432234/architecture-risk-2012.pdf"
|
||||
}
|
||||
],
|
||||
"pdf_sha256": "0a56a490557e1f97ac9f1b0999203acdb980f244d745bf8f211f40763af2be49",
|
||||
"pages": 6
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue