Category: Uncategorised

Orphan Black's fourth season premiere aired last Thursday, so we're taking this opportunity to dissect the popular show's game-changing episode and how it may affect the series from here on out. As such, we've included some, but not all, of the episode's plot spoilers, which begin after the first big-bold text heading below.

You’d be forgiven for turning your nose up at the idea of getting involved with a long-running sci-fi series. It's usually somewhere around a show's fourth season that a producer or showrunner decides it’s time for things to shake things up. It’s the fans’ fault! They’ve already made it clear that they’ll stomach a show’s decision to bend the rules of science and logic. Surely they’ll accept just about any cockamamie twist, right? Let’s kinda-sorta kill Starbuck or add some Kromaggs!

Yet of all modern, long-running sci-fi out there, Orphan Black might be in the best position to endure such a shake-up right now. The clone-obsessed series stumbled through the earlier episodes of its third season last year, especially as it focused on boring villain Dr. Coady, and Delphine’s turn as a Dyad executive, and a bunch of other Dyad plot gobbledygook. Eventually, the BBC America and Space co-production returned to the source of its initial charm: its star. Orphan Black has always shined by mining world-collision moments for both drama and humorous effect, as various clone-carnations of lead actress Tatiana Maslany contend with the other clones’ idiosyncrasies (not to mention their odd friends and family members). Orphan Black got back to this, and it tied a surprisingly neat bow on some of its hokey clone-brother plots.

Networks may look different, but the security problems are basically the same.

The National Security Archives at George Washington University has just added a classic text of computer security to its "Cyber Vault" project—the original version of what came to be known as the "Ware Report," a document published by the predecessor to the Defense Advanced Research Projects Agency in February 1970. And as much as technology has changed in the 46 years that have passed, the Ware Report would still hold up pretty well today with a few notable edits.

The document, officially entitled "Security Controls for Computer Systems: Report of the Defense Science Board Task Force on Computer Security," was the result of work undertaken in 1967 at the behest of the Advanced Research Projects Agency (ARPA, now DARPA) to deal with the risks associated with the rapid growth of "multi-access, resource-sharing computer systems"—the primordial network ooze from which the Internet would be born. Authored by a task force led by computer science and security pioneer Willis Ware, the report was a first attempt to take on some of the fundamental security problems facing a future networked world.

The Ware Report included a list of conclusions and recommendations that (based on recent data breaches and security failures) many have failed to take to heart. The first of these is one that recent ransomware attacks seem to show that organizations have forgotten. "Providing satisfactory security controls in a computer system is in itself a system design problem," Ware wrote in the summary memo accompanying the report. "A combination of hardware, software, communication, physical, personnel and administrative-procedural safeguards is required for comprehensive security. In particular, software safeguards alone are not sufficient."