Spy Files 3
From the gist of the incredible difficult to decipher training manual there are 4 systems. Overview of network topology is here:
<a href="http://i.imgur.com/gzw6nAT.png" rel="nofollow">http://i.imgur.com/gzw6nAT.png</a><p>1) ADMF-Client & Infection GUI<p>These seem to be HP Compaq computers, running Windows 7 Ultimate, FinFlyISP GUI and a XMPP client(which runs over TLS and is secure).
This is a tool for LEA to use which interfaces with the ADMF backend for managing infections, selection of infection methods, realtime status info and management of all components.<p>2) ADMF - Central Administration Function<p>This is the backend which all the LEA terminals in 1 connect to. These are HP DL380 G6 Intel Xeon X5550 @ 2.67GHz servers  running hardened Debian(by Dreamlab best practices). It is a core component of their infrastructure and communicates in realtime with all their other component systems. It stores the configuration and initiation of infections. Realtime exchange of info and states(target coming online, being infected, etc.) Contains RFC XMPP used for secure encrypted communications.<p>3) Network Data processing component (iProxy/NDP01/NDP02)<p>Infections are remotely activated by ADMF in 2 via the GUI. Each NDP is bridged with 10GB/s fiber bypass module. Incase of hardware/logical failures this module switches automatically to by-pass mode. Thus traffic will never be interrupted. ATTENTION this is highly dynamic bridge, do not change any configuration manually. <i></i>NDP has been specially configured for his network, any changes are tightly coordinated with Dreamlab.<p>4) Radius Probe(RP01/RP02)<p>Realtime monitoring of AAA processes which include:<p>1. Targets coming online<p>2. Receiving IP Addresses<p>3. Changing IP Addresses<p>4. Going offline<p>Recording of RADIUS authentications and accounting dialogues. Being always up to date of target IP
RP sends info to ADMF, the ADMF provisions the NDP. Running same hardware/OS as 3. The RPs have bidirectional connection with broadband remote access server(BRAS) [1] which are what connect to the global internet from a ISPs network. BRAS aggregrates user sessions from access network. This is where ISPs can inject policy management and QOS. Aggregrates DSLAM connections from locally dispersed in an ISP area network.<p>Communications Visualized<p>The slide explains that communication of all components always is initiated towards the ADMF.<p><a href="http://i.imgur.com/qOQfVYd.png" rel="nofollow">http://i.imgur.com/qOQfVYd.png</a><p>Use Cases<p>1. GUI->ADMF [Infect a target]<p>2. ADMF->Radius prove [Start monitoring/set a trap on target]<p>3. Radius->ADMF->NDP/iProxy [Handover of IP]<p>4. iProxy->NDP [iProxy requests NDP to analyse datastream on IP and "interesting" traffic]<p>5. NDP->iProxy [Handover traffic matching request]<p>6. iProxy [changes traffic and modifies data by adding infection parts]<p>7. iProxy->NDP [iProxy sends modified traffic data to NDP]<p>8. NDP Reinject [NDP recalculates checksums/resequences TCP/IP packets and reinjects traffic into the stream]<p>9. Target infection done [Data successfully sent to target]<p>[1] <a href="http://en.wikipedia.org/wiki/Broadband_Remote_Access_Server" rel="nofollow">http://en.wikipedia.org/wiki/Broadband_Remote_Access_Server</a>