We heard of XKeyScore, well here’s the rest of the NSA’s secret tools and their codenames.

1. Cloud/ABR
2. DISHFIRE
3. FASTSCOPE
4. Marina (SSR)
5. OCTAVE
6. PINWALE
7. SIGINT NAVIGATOR
8. TRACFIN
9. TRANSX
10. TUNINGFORK
11. UTT
12. XKEYSCORE
13. SPYDER
14. CHALKFUN
15. STELLARWIND

This information was once TOP SECRET/COMINT/NOFORN, well it’s not anymore. The complete audit report of the many Database query incidents, and errors made by the NSA employees during the first quarter of 2012. The document was published by the Washington Post and was an interesting read to say the least. In other news, Lavabit’s owner Ledar Levison hinted that he was issued a National Security Letter of sorts, which one would guess was actually signed by FISA for him to give up any information he had on Edward Snowden. He basically went on Democracy Now to attempt to explain why he was shutting down his semi-secure email service.

Microsoft Solutions Framework Process Model

The MSF version 4 process model includes 6 phases.
1. Planning – Agree on the goals and scope that are required for your deployment. You should document the specific features, services, and configuration options that are necessary to achieve these goals. You must document a master project plan, which describes how the implementation will proceed, along with a master project schedule that will be approved at the completion of this phase.
2. Building – This phase includes the development of the Windows Server infrastructure, including any custom code and applications or scripting required for the day to day function of information technology in the organization. Management marketing materials and end-user communications are developed with the goal of selling the idea of the project to the organization or consumers. Test specifications, cases, metrics, scripts, and data are also developed as are the initial operations guides, support procedures, knowledge base, and troubleshooting documentation.
3. Stabilizing – Build out the deployment in a lab environment utilizing virtual machines, and thoroughly test all possible complications before deploying in the production environment. In this phase it is essential to ensure that the platform is stable, before you begin to implement the pilot deployment.
4. Deploying – Finally, you deploy your Windows Server and/or System Center deployment into the production environment in a small supervised pilot project with the IT staff notified of all necessary tasks to complete. If this initial deployment is successful, you can begin to roll out the rest of the server infrastructure to the production environment. During this phase, revise processes and procedures wherever necessary, perform end-user and administrator training, and document all configurations. Create a repository for all final documentation.
5. Governing – The IT management team will be responsible for developing a project charter from project inception to completion and beyond, and for providing team guidance. They will track the project status, status of project deliverables, and user satisfaction after the project is deployed. They will be responsible for documenting the closing out of the project, and any next steps to take should be developed in a road map, while documenting the lessons learned.

For more information on the Microsoft Solutions Framework, you can check out this page on MSDN.