. @dguido @sk3wl @sergeybratus Just noticed you three are on the @polyswarm advisory board. What level of involvement do you have and are you planning to integrate your businesses into the ecosystem?
-
-
Have you worked with any of their team before they started
@polyswarm? Sorry if the answer is confidential. -
Yep!
@trailofbits and@NarfIndustries (the tech team behind@PolySwarm) worked on DARPA's Cyber Grand Challenge, a fully autonomous hacking competition: https://dtdnnp-01.darpa.mil/program/cyber-grand-challenge …@NarfIndustries wrote some of the challenges and@trailofbits solved them :) -
So initial roadmap looks like it's just for file analysis? Are you planning to expand to other data types like domain/IP/hash/etc? Complex types like composite TTP IOCs? If so, how's that fit in with your existing roadmap?
-
1/ Great question, 2 part answer: 1. We're initially considering artifacts that cannot change from under us. A file that was malicious on Day X will also be malicious on Day Y. This is not necessarily true of a domain name or IP which may swap what it's serving. We're interested
-
2/ in creating a ledger of malintent, so we are looking at static artifacts. 2. In general PolySwarm transacts in only the output of a detection engine. At first, that'll be a boolean: malicious/benign. Later, we'll explore consensus around, e.g. malware families. PolySwarm is
-
3/ not focused on transacting in the signatures / heuristics that produce that output. That's each security expert's secret sauce that they continually hone (and keep private if they wish).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.