There is a mention of security in one of the paragraphs, and it is only because the people running the testing platform have to make certain that you can't use a bug in the automated browser framework (Selenium) they are using to take over their network. When I read this title (which was modified from the original for HN) it made me wonder "how is security a key selling point for a testing framework", and then I found out that it wasn't ;P.
As a customer, security is important when you are testing your internal, firewalled, infrastructure. This is one of the main reasons Sauce Labs (where I work) gives every test its own VM that's destroyed afterwards. Using a shared or reused VM opens the door to malicious code running in the background.
Interesting: thanks for that perspective; to be clear, the reason I commented on this at all is because the title didn't make it clear why the security was interesting and the title was different from the title of the article (which is part of a massive debate about whether editorializing of titles should happen on HN; currently, the rules say you shouldn't do it, but personally I think it might be important in numerous occasions), but then the article itself didn't seem to indicate that the security was actually that key to the whole thing. (In particular, the one phrase "highly secure" that is used in the first sentence of the last paragraph seems like a frill to make the sentence sound more awesome: it didn't come after any motivation about how this is a key problem with other solutions, or that that is why the "enterprise" tag is on the idea.) Again: thanks!
