Thursday, November 29, 2018

An all too common error. This happens when you follow “Worst Practices.” Or, more likely, “No Practices.”
Catalin Cimpanu reports:
An ElasticSearch server that was left open on the Internet without a password has leaked the personal information of nearly 57 million Americans for almost two weeks, ZDNet has learned.
The leaky server was spotted by Bob Diachenko, Director of Cyber Risk Research for cyber-security firm Hacken, during a regular security audit of unsecured servers indexed by the Shodan search engine.
Read more on ZDNet.




What makes these scams worth the effort? 6% of victims pay up!
That Virus Alert on Your Computer? Scammers in India May Be Behind It
You know the messages. They pop up on your computer screen with ominous warnings like, “Your computer has been infected with a virus. Call our toll-free number immediately for help.”
… Most people ignore these entreaties, which are invariably scams. But one in five recipients actually talks to the fake tech-support centers, and 6 percent ultimately pay the operators to “fix” the nonexistent problem, according to recent consumer surveys by Microsoft.




As one of the lawyers at a recent Privacy Foundation seminar quipped, “The EU took seven years to write the GDPR. California took seven days.” It shows.
FPF and DataGuidance Comparison Guide: GDPR vs. CCPA
The General Data Protection Regulation (Regulation (EU) 2016/679) (‘GDPR’) and the California Consumer Privacy Act of 2018 (‘CCPA’) both aim to guarantee strong protection for individuals regarding their personal data and apply to businesses that collect, use, or share consumer data, whether the information was obtained online or offline.
… As highlighted by this Guide, the two laws bear similarity in relation to their definition of certain terminology; the establishment of additional protections for individuals under 16 years of age; and the inclusion of rights to access personal information.
However, the CCPA differs from the GDPR in some significant ways, particularly with regard to the scope of application; the nature and extent of collection limitations; and rules concerning accountability.


(Related) Another way to measure the significance of the GDPR.
UK fine against Uber for 2016 data breach would be 200 times bigger in 2018
Uber’s widely publicized data leak from two years ago has finally resulted in a fine from the UK Information Commissioner’s Office. The penalty would have been 203 times the amount if the leak had occurred this year, after the GDPR era took effect in May.
“The Information Commissioner’s Office (ICO) has fined ride sharing company Uber £385,000 for failing to protect customers’ personal information during a cyber attack,” reads the announcement. In US dollars, that figure translates into around $492,000.




I admit that I never understood James Joyce. Perhaps this will help?
Understanding Great Works: a new research tool on JSTOR
Understanding Great Works (Beta) is a free research tool from JSTOR Labs that fosters student engagement with classic literature by connecting passages in primary texts with journal articles and book chapters on JSTOR that cite those lines. Building on the success of the Understanding Shakespeare tool, Understanding Great Works encompasses several key works of British literature such as Frankenstein and Pride and Prejudice, the King James Bible, as well as all Shakespeare sonnets and plays. These initial texts have been selected in collaboration with Studies in English Literature and JSTOR Labs plans to add new ones monthly; we invite you to vote for the texts you’d like to see next. Understanding Great Works is a powerful starting point for research within the primary source; the tool makes it easy to find academic analysis for literary texts and encourages close reading. The literary texts are open access on JSTOR, but an institutional or individual access account may be required to view the full text of the linked journal articles and book chapters.
Understanding Great Works is integrated on the JSTOR platform and easily accessible from the “Tools” menu on the top of each page. The tool is being released in a beta status, which indicates that the tool is publicly available but we are actively testing and updating the features. A companion LibGuide is also available. If you experience any problems with the site or have feedback, we encourage you to contact us at labs@jstor.org.”




Not really ‘anything,’ but lots of things. Tools for my students.




Other useful stuff.


No comments: