We're building a full-on cyber risk management platform encompassing not just insurance, but threat intelligence and other cyber security tools to help our customers prevent loss entirely. We're also assembling a team of expert incident responders, threat and malware researchers, and security analysts to protect our customers before, during, and after a cyber incident.
We're a high growth startup and we've recently secured a large round of funding (https://news.crunchbase.com/news/coalition-secures-90m-serie...), we have many projects and tasks that you can take on, depending on your preferred area of focus.
We have a few priority roles we are actively hiring for:
you can also checkout app.binaryedge.io for more data like this from other countries! it's crazy the amount of stuff that is out there. to me the most baffling is still the amount of DBs with customer information on 'em
If one wanted to go about simulating one of these in a homelab what sort of hardware would your recommend that is price accessible? even if a smaller mesh like 20-30 nodes.
The Cooja simulator runs nicely on a regular laptop and could then run up to some 50 nodes at real time speed. For larger networks, a larger computer is needed. Alternatively, the simulation speed can be reduced. The simulation detail level also affects the speed. With a highly detailed simulation, with device microprocessor and radio transceiver emulation, a normal laptop can handle some 10 nodes before it starts to slow down.
10 years ago I built a streetlight system, we implemented and tested the protocol by build a simple simulator in a qt app and embedding the same software stack inside it, it allowed us to create models that modelled x/y locations, distance signal drop off, random noise, exit points etc
Large randomly placed simulations only started to slow with ~15k nodes ... In other words it's not hard
Probably not that useful in that it was an old QT, no longer compiles.
More importantly I have a tiny OS that doesn't have real threads (code had to run on 8k), I port it all over it simply consists of a timer queue, and one stack - threadlets are a queue entry with a data pointer - running 14k instances of this tiny OS in one simulator is pretty easy (you still just have one timer queue ....) - so you can see it's all pretty dependant on the uOS
The only hard part is making packet delivery not O(N2)
On a quick scan that looks like interesting analysis. Though one point that I find most run-downs like that miss is the number of accounts that are throw-aways, where the user simply doesn't care and will never use it again. At that point using "123456" or "password" isn't an issue, anyone who hacks the account gets nothing more than they would get if they just created a throw-away account themselves.
The hacker can grief / spam everyone else in the system from this "normal" account. Depends how much public interaction / content posting there is, though.
True, but this is not really a problem for the user, but a problem for the system. It is reasonable to assume that the user that creates these type of accounts does not really care about the security of the system either.
Coalition operates as a cyber insurance and security company that helps businesses manage and mitigate cyber risks.
For positions available: https://jobs.lever.co/coalitioninc