app:tlsfingerprint
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
app:tlsfingerprint [2017/11/28 23:56] – [Analysis of TLS Fingerprints] veera | app:tlsfingerprint [2017/11/29 15:14] – vivek | ||
---|---|---|---|
Line 39: | Line 39: | ||
- | ===== Analysis of TLS Fingerprints | + | ==== Analysis of TLS Fingerprints ==== |
What are you going to do with these prints. There are a few options | What are you going to do with these prints. There are a few options | ||
Line 51: | Line 51: | ||
- | ===== Using Trisul streaming analytics | + | ===== How the TrisulNSM App works |
- | Since we do not yet have many malware fingerprints, | + | The TLS Print app is written in LuaJIT and plugs into the TrisulNSM Scripting Engine. The source code for the App is available |
- | | + | The app generates the following pieces of info. |
- | - Graph Analytics : When a Print is seen , the edge vertices namely the IP Flow Tuples, and the SNI (Server Name Indication) Extension are added. | + | |
- | - Alerts : Right now we dont have many Malware prints, but when we have them, the App can generate an alert. | + | |
+ | - **Graph Analytics** : When a Print is seen , the edge vertices namely the IP Flow Tuples, and the SNI (Server Name Indication) Extension are added. | ||
+ | - **Alerts** : Right now we dont have many Malware prints, but when do we have them, the App can generate an alert. | ||
Line 93: | Line 95: | ||
When you reveal adjacent vertices in [[https:// | When you reveal adjacent vertices in [[https:// | ||
- | ==== Programatically resolving TLS Prints ==== | + | ===== Programatically resolving TLS Prints |
- | The TrisulNSM TLS-Print | + | This App dumps all fingerprints |
- | + | We invite | |
- | If you can access | + | |
- | + | ||
- | + | ||
- | + | ||
app/tlsfingerprint.txt · Last modified: 2018/03/04 13:27 by veera