Monday, 12 January 2015
European CommissionThe DPD was proposed by the European Commission in 1990, and adopted in 1995. The GDPR was proposed by the European Commission in Jan 2012, as part of a data protection reform package, to update the DPD.
The following diagram shows the number of Articles, Recitals and pages of legislative text (ie excluding explanatory commentary/notes, background material) in the 1990 DPD draft as compared with the 1995 DPD and the 2012 GDPR draft:
(Note: the 1995 DPD page count is not included as no "like for like" comparison is possible - the Official Journal PDF is 2-column and the font size, spacing etc are different.)
If you like, the vital statistics for the DPD (original 1990 proposal) and GDPR (1992 Commission proposal) are respectively:
- DPD (1990 proposal): 33-24-27
- GDPR (2012 proposal): 91-139-82
Before the GDPR can become law, it must be approved by both:
- the European Parliament, ie elected MEPs, and
- the Council of the EU aka Council of Ministers, ie EU national governments.
In the European ParliamentThe Parliament's lead committee appointed to scrutinise the GDPR was its Committee on Civil Liberties, Justice and Home Affairs (LIBE, rapporteur Jan Philipp Albrecht). LIBE's report to Parliament suggested numerous amendments to the Commission's text, taking account of input from several other Parliamentary committees including various amendments they proposed. Parliament adopted this unamended at its 1st reading of the GDPR on 12 Mar 2014.
The infographic below shows, for each of the DPD and GDPR, the number of amendments proposed by Parliamentary committees and the number of amendments actually approved by Parliament at its 1st reading.
In the CouncilThe Council of Ministers (comprising EU Member State national government ministers and the Commission) has, from the outset, been trying to agree its own position internally. Approval by the Council requires only a qualified majority vote rather than eg unanimity. Only after a draft text has been settled within the Council, can the task of agreeing a text with Parliament begin. It won't be easy: even now, there are many significant differences between the Parliament and latest Council versions.
Numerous Council documents have been released, many on specific parts only of the draft GDPR. As at Jan 2015, only three versions are available of the full consolidated draft GDPR text being discussed in Council - two officially published, the latest one leaked. The diagram below compares the number of footnotes in each consolidated draft version. The number of footnotes is used as a rough indication of the scale of Member State issues with the GDPR text, as most (though not all) footnotes contain reservations or similar statements by Member States or the Commission.
Number of EU Member StatesDuring the passage of the DPD, there were 12 EU Member States (becoming 15 on 1 Jan 1995, when Austria, Finland and Sweden joined).
When the GDPR was proposed by the Commission on 25 Jan 2012, there were 27 Member States (becoming 28 on 1 July 2013, when Croatia joined). So now there's nearly double the number of Member States as there was in the 1990s, to raise and agree issues in Council.
TimelineThe figure below compares the timelines of the DPD and GDPR.
Official statements have been made signalling the aim of agreeing the GDPR by the end of 2015 or even earlier, eg:
- Vice-President for the Digital Single Market Commissioner Andrus Ansip: "During the first six months of the Commission’s mandate, I will support Commissioner designate Jourová and work with you and the Council to finalise the reform of data protection rules".
- Commissioner for Justice, Consumers and Gender Equality Věra Jourová: "I see it as an important project of the whole Commission to ensure the swift adoption of the EU data protection reform… I strive for the adoption of the European data protection reform package within the first six months of the mandate".
- Commissioner for Digital Economy and Society Günther Oettinger: "my legislative priority will be
to support the Vice-President for the Digital
Single Market and the Commissioner for
Justice, Consumers and Gender Equality in finalising the negotiations on an ambitious Data Protection Regulation in 2015…".
- In the Council, in early Dec 2014, "Progress was made by justice ministers on the EU data protection framework…" and the Council's President Andrea Orlando said "Today we have agreed on two of the most politically sensitive issues on data protection reform. We see this as an important result for the Presidency, and a decisive step towards achieving global agreement on this complex and important file"
- The Commission recently stated "In 2015, as part of the Digital Single Market Strategy, the Commission will aim to conclude ongoing inter-institutional negotiations on proposals such as the common European data protection reform and the Regulation on a Connected Continent."
- Calls were made by several national Parliamentary delegations for adoption "by 2015". Parliament's motivation to ensure the GDPR goes through may well be bolstered by the reincarnation of GDPR instigator Commissioner Reding as an MEP (Member of European Parliament) who, as Martin Hoskins irreverently puts it, may not want to pass up "the opportunity of being forever associated with a once-in-a-generation opportunity to reset data protection rules".
- the number of Member State issues within the Council, as suggested by the number of footnotes;
- the far greater number of Member States there are now than in the 1990s; and, not least
- the current vast differences between the texts propounded by Parliament and Council, which will have to be bridged somehow.
SummaryThe figures from the diagrams above are consolidated below in a single infographic.
controllers and processors. See for example Chris Pounder's concerns regarding greater flexibility for Member States to make their own rules, particularly more national exemptions from data protection law requirements. I hope to blog my own specific concerns at a later date.
We need better laws, better enforced by better-resourced regulators. And by "better laws" I mean sensible, realistic, understandable, clear, technology-neutral laws. It remains to be seen whether the GDPR will achieve that goal.
ParliamentFigures for the DPD are derived from:
- the report of the lead committee for the DPD, the Committee on Legal Affairs and Citizens' Rights (JURI) PE 148.286/fin A3-0010/92 15 Jan 1992, rapporteur Geoffrey Hoon. This refers to PE 148.286/rev./Am.212-293, ie 293 amendments were proposed by that committee, and appends opinions of other committees showing their proposed amendments: ECON 39, ENER 9, ENVI 22
- Parliament's resolution and amendments 11 Mar 1992 (OJ C 94/173, 13 Apr 1992).
- Parliament's GDPR Q&A page, Facts and figures section (see also LIBE's document list/links)
- Parliament's resolution of 12 March 2014, on 1st reading.
CouncilFigures for the DPD are derived from:
- 9951/94 (12 Oct 1994);
- 11099/94 (30 Nov 1994).
GeneralFor a very readable book on how laws affecting the Internet should be made if they are to have any chance of being effective in practice, see Chris Reed's excellent "Making Laws for Cyberspace".
Wednesday, 20 August 2014
Available in the US from 2013, Google Glass Explorer Edition arrived in the UK in late June 2014 - still in beta, so buyers are “Explorers”, and Glass’s software is continually being updated (release notes and see this link). Glass won’t be available for consumers generally for some time yet.
I tried a demo unit (linked to dummy Google account) in Google’s London showroom, assisted by a “Glass Guide”. Offers to pawn my immortal soul couldn’t garner me a loan. I didn’t get to wear it outside, so couldn’t experience others’ reactions to Glass.
1. What’s Glass?A £1000 (incl. VAT), Android 4.4 KitKat wearable computer inside a 43g “headband”, worn like glasses: 5MP panoramic camera (720p video), 12 GB usable storage, 670 mAh lithium-ion battery, accelerometer/gyroscope (not stated in the specs but there must be one given how it works), wi-fi and Bluetooth (official specifications, additional info). Processor and RAM are not mentioned in the official specs, but a public Google+ post stated that new units will have 2GB RAM.
The titanium frame and nosepads are adjustable (press and hold). 5 colours are available (but no left-handed/eyed version) – see various photos.
1. Bone conductor transducer (“speaker”) – press it to your skull to hear more clearly. I had trouble although the volume was maxed, so the supplied earbud is indispensable in noisy settings. (The CPU and battery are inside the arm bulge – can get hot!)
2. On/off button power - inner side of headband. Press once to deactive/sleep Glass, press and hold to power up/down.
3. Touchpad – outer side of the headband’s right arm; a horizontal touchstrip rather than “pad”, stretching between components 2 and 4 in the diagram above.
4. Camera (the “shutter” button’s on top) and microphone (black vertical strip, inner side).
5. Display (monitor substitute) - a small transparent cuboid on a hinged arm. Look up to the right to view the “screen”; Google analogises it to looking in a rear view mirror (at least for US drivers). Once adjusted properly via the hinge, it’s like viewing a 25” HD display from 8 feet away. Only a few lines of text are displayable.
Micro-USB port - beneath 2(ish), for micro-USB cable or earbud:
There's no hard volume control buttons – although you can change the volume in Settings, while listening to music, or during a phone call.
Here’s another view:
3. BasicsYou can only buy one Glass per Google Account. If you need prescription lenses, you can get a special frame free with your Glass purchase, which Glass screws onto (see photo above). Or free shades instead, if you prefer.
In the box: Glass, pouch, micro-USB to USB cable (for charging, or connection to computer to access photos/videos), mono earbud (+£60 for stereo ones), 2 pairs of spare nosepads.
Warranty: 1 year.
Battery life: meant to be a day; intensive use eg video recording obviously affects that. Charges overnight. Sleeps (screen fades etc) some seconds after you stop interacting with it, to save battery life; tap touchpad or tilt head up to wake it. You can't change the sleep time.
Accessories (pay extra): eg shield, stereo earbuds, case, spare frame (scroll to the bottom of this page).
MyGlass app (iPhone / Android): effectively required, as some functions aren’t possible without it. Accessing the MyGlass website through a computer works, but that’s obviously less portable. You can install MyGlass without having Glass, but you won’t get far!
4. Buy?You need a Google account and credit card. Lasiked? Best check with your doctor first.
- Google’s King’s Cross Glass showroom (locked, with beefy security guard). By appointment only. But if you wander by and press buzzer looking pleading and winsome, they might just let you in.
- (Better bet) buy online (also see this) - there are standard terms of sale.
5. Play, not buy?
- Updated 23 Aug: Get a demo - you can now book one via https://glass.google.com/getglass/visit/GB (though it's not entirely clear if you can book an appointment just to try, rather than to buy)
- Buy, try, return within 30 calendar days for full refund (NB wipe it first!).
6. Controlling GlassOn wakeup you’ll see the home screen (strictly, home “card”) showing the time and “OK Glass”.
Voice commands: while viewing the home card, say “OK Glass” to call up menu (nod up/down to scroll vertically); say menu option name.
Speak clearly and slowly, voice recognition isn’t perfect! When composing a message etc, it transcribes voice to text, but you can’t correct just the last word - you’ll have to start over.
Touchpad: used for many functions, eg tap to activate/OK/wake from sleep. Recognises tap and swipe forward/back/down (not up). Down means back/"escape"/home. For many menus you need to keep swiping for the next option.
Bluetooth keyboards may work, with tinkering (eg this link and this link). Google itself has patented a projected virtual keyboard. Someone’s produced a touchpad-controlled on-screen keyboard. People are working on remote controllers for Glass via Bluetooth (another example), maybe even full-size virtual keyboards (via bracelets).
7. Functions/featuresGlass is integrated with Google’s services, unsurprisingly. So, Google services will “push” emails/notifications etc on-screen. Functions include:
- Search – say “OK Glass. Google [search term]”. (Interesting given Google’s trademarks battles to stop “Google” becoming a generic term for “search for Internet stuff”!)
- Browsing - you can view websites found through searching, but not by spelling URLs.
- Watch/listen to YouTube videos (again, search for them).
- Make/take calls – works as a Bluetooth headset, if paired. Android/iPhone recommended.
- Gmail – get notifications of newly-arrived emails to read, reply, star, archive, delete.
- Send messages, photos etc – not just via Gmail but also Hangouts, SMS (Android only, not iOS). You need MyGlass to select email as a method. Talk, and text appears!
- Google Calendar – see events for next 2 days, edit events, etc. I’m told events can be added too.
- Google+ - view notifications, +1 or comment on posts, start or join video calls, share photos/videos with contacts/circles
- Take photos “with some software improvements, like HDR” – 3 options (preview via a “viewfinder”):
- voice command
- “shutter” button
- (when that setting’s enabled) wink. Warning: blinking may result in inadvertent snaps…
- Record video – stops after 10 seconds unless you continue it (no audio recording's available, unless someone writes an app).
- Share photos etc – via Hangouts, Google+ etc; post videos direct to YouTube.
- Navigation/directions – see 10.
- Google Now – “in-the-moment information based on your Google Now Settings”, including Weather, Stocks, Sports, and Flights. Includes notification of Now reminders, supposedly even finding where you’ve parked your car. This function seems potentially the most useful, but there’s obvious privacy implications – no room to discuss them here.
- Translate foreign signs (Word Lens - amazing and currently free! Also on iPhone; Android Play Store).
- Google Play Music – listen to your Play library music.
- Screencast to Android tablet/phone – mirrors Glass display via Bluetooth.
- Transfer photos/videos to computer – Glass behaves like a camera, when connected via cable. Only photos/videos are accessible in this way, but Google may change that if people would like access to other files. You can copy, rename, or delete photo and video files. However, renaming them will make them no longer available in the timeline (covered later). You can’t manage the files on Glass through your computer beyond that.
- Backups – when Glass is charging and connected to wifi, an autobackup feature (enabled by defaul) will automatically sync photos/videos to a (supposedly private) folder or “album” on your Google+ account (without deleting them from Glass), and also autoupdate itself. I'm told that no other items are synced to Google+, currently. You can force initiation of backup manually. Stopping Glass autobackup from automatically copying your “private pictures” to Google+ seems much trickier - a setting to disable autobackup would benefit privacy-conscious users. Another issue seems to be that deleting media from Glass, to free up space, deletes it from G+ as well (ie it syncs rather than backs up), which may defeat the object of backups. I'm told that:
- An autobackup "clear" function removes items from Glass that are already backed up, but leaves backups intact.
- Deleting photos via a timeline card – deletes from both Glass and online
- Deleting from Glass via connected computer – deletes only from Glass.
- Have it read emails etc aloud. It can also describe aloud what you touch, select etc.
8. UseA “card” fills the screen, eg home card, settings, calendar event notification, email/SMS notification, photo snapped, news event pop-up. (Experimental) “notification glance” opens the email etc on glancing up after receiving the notification. When notifications arrive, Glass also chimes.
Texts and emails are copied to internal memory and the timeline. As stuff happens or you do things, cards get saved to a “timeline”. New cards “push” older cards to the right. Scroll through cards in the timeline by swiping back/forwards. Related cards can be grouped in a “bundle”, eg Settings, upcoming calendar events. Cards are removed from the timeline in 7 days/after 200 cards. Check the timeline to view any notifications arriving during sleep.
9. Apps (“Glassware”)Unlike Google Play/iTunes apps, the Glassware Gallery of (Google-tested/approved) third party apps, ie “web services that can send content to and from Glass”, is accessible only through Glass + MyGlass. Glassware (unofficial directory, about 60 so far) includes Shazam music recognition, Twitter, Evernote, Guardian and other news apps, etc. No apps yet for speech to text notes (although you could email or text yourself a note), or PDF/Ebook reading, and porn apps were banned! There’s help/info for developers, including a downloadable SDK (software development kit), and current development seems particularly focused on medical applications.
10. Limitations/issuesPerfect vision or contacts is best. Myopic me couldn’t see anything without holding it over my regular glasses.
But, it’s not designed to fit over specs. So you need a special frame (currently free if buying Glass, +£175 per extra frame, 4 styles available); then go buy prescription lenses, pay specialist opticians, pay again if your prescription changes. Again there’s a range, including shades.
MyGlass seems essential for some basic functions eg Gmail contacts, selecting how to send stuff (email, SMS etc – no SMS option with iOS). In my view Glass alone isn’t enough; ideally you need an iPhone or (better still) Android smartphone, to use Glass to its fullest with MyGlass.
It’s uncomfortable (even painful) to keep looking up/right continuously. Google recommends trying it for 30 mins the first day, then building up. However it’s not meant for prolonged continuous use, but for short “micro-interactions”, so as not to distract you too much while hot air ballooning (as you do). That’s why the display’s small, Google says.
Even during my demo, a “Glass must cool down to run smoothly” message appeared; it downed tools, needing at least a minute’s rest before working again. I didn't time it, but my continuous use couldn't have been for more than 20-30 minutes when that message appeared, probably less. Can’t see how you’d video a full-length movie, despite cinemas’ fears!
Environment - with ambient noise, eg someone speaking loudly at the other end of the room, it’s hard to hear without the mono earbud. In bright sunlight, the display may be hard to see.
Navigation/getting directions requires a Bluetooth-paired GPS-enabled phone. Most other functions/apps need connectivity. For Glass to join secured wifi networks, use MyGlass on your linked phone or the Glass website on a computer. Otherwise, Glass can only join open wifi networks (as there’s no keyboard to enter passwords). But you can tether Glass to your phone via Bluetooth or wifi to use your mobile data plan, if your network allows it. A few apps don’t need connectivity, like Star Chart.
You have to trawl through the timeline to find things. There’s no timeline search, no structured way to access saved data eg “all photos”, “all emails”, etc. There’s no file manager eg to delete photos in bulk, even via MyGlass, though you can “clear” all media stored on Glass in one go.
11. SecurityThe screen’s transparent. People can see what you’re seeing - if they peer closely and can read reverse text. You’d notice! Similarly, they’d have to be uncomfortably close to hear anything, or to issue voice commands that would be recognised (voice recognition is not tied to the individual user).
To secure Glass better and deter Glass-snatchers:
- Set a screenlock code: a sequence of 4 steps, each comprising 1 of 10 different options: tap, swipe forward, swipe back, hook swipe forward, hook swipe back, each of which can be done with 1 or 2 fingers, giving 10,000 possible screen lock (or, strictly, unlock) patterns. Glass automatically locks after about 5 seconds’ inactivity, or on touching the power button, and if you've set a lock code then you'll have to enter the correct pattern to unlock it on waking it after sleep.
- Set “On head detection”, so that Glass automatically deactivates on removal, whether by you or a would-be Glass thief (and it wakes on putting it on).
However, be warned that photos/videos stored on Glass are easily accessible just by connecting it to a computer, even if you've set a screen lock code. Also, texts and emails etc are stored in internal memory. If someone stole your Glass, I don't know how easy it would be to retrieve your emails etc too. If Glass offered full disk encryption (FDE) and you enabled it, that would scupper snoops or at least make their life much harder.
Google wouldn't tell me if Glass has FDE or not, but given the accessibility of photos/videos through USB, I imagine not. As Android tablets/phones offer FDE (albeit crackable), I hope Google will start supporting this for Glass.
The good news is that apparently people using Glass in sensitive settings (financial, government etc) can program Glass to their requirements. Eg Google said developers could change the voice command from “OK Glass”.
Google may deactivate your device if you tell them it’s lost/stolen, but that doesn’t delete data. However, Google says you can erase your device remotely via MyGlass or the Glass website, which wipes the device as soon as it connects to a network thereafter. A factory reset is possible through the Settings also. I don't know how thorough the wipe is - Google didn't tell me if that zeros all (or indeed any) data, how many passes are used etc, and how easily retrievable data may be after the erasure. But reportedly a reset doesn't fully wipe some other Android tablets or smartphones (Avast report including link to free app to overwrite files), and no overwriting app for Glass appears to be available yet.
12. (Other people’s) privacyPeople can see when the screen’s active (lit up) even from a distance. Though you could just be viewing a notification. They can’t tell if you’re taking a photo or recording a video unless you press the shutter button or wink. But any extra "mind control" headset's pretty obvious, and extending a video recording beyond 10 seconds requires tapping (though again you might be tapping to do something else). Glass can even be used to read other people’s phone/tablet passwords!
As for Glass users’ privacy (eg metadata saved with photos) and developer issues, that’s for another article (for space reasons), but I'll say for now that I was told no GPS location metadata is automatically saved with photos – though date/time data are saved (see details of the types of metadata automatically recorded with Glass photos).
Does it make you feel constantly connected, or just connected whenever you wish to be? Is it intrusive / disruptive to your life having them always there, or is it just convenient? As it goes to sleep quite quickly, it’s only connected intermittently. Subject to the overglasses point below, they wouldn’t feel intrusive or disruptive to me. Eg if notifications would be disturbing during a meeting, just put it to sleep until you’re ready to receive them. Whether others might find it intrusive is a different matter! Anecdotally I’ve heard of someone removing them and putting them round his neck, clearly inactive, before entering the men’s room. That might be part of evolving etiquette.
What unstructured data would you want it to structure? I didn’t quite follow this question. It’s meant for use on the go, receiving useful info like email notifications, or taking photos/videos hands-free – it’s not designed for structuring data (and see my file management/search points).
Other questions – (including by private message) were mainly on data/content and rights, which for space reasons I’ll cover in a separate future article.
14. If only…No frame’s available that’s designed to fit over one’s regular glasses. A Googler suggested that perhaps overglasses were thought unfashionable. True, some overglasses are functional, but others can be quite blingy. And some people can’t or don’t want to wear contacts or buy another frame just to use Glass. I think more people would buy Glass, who wouldn’t otherwise, if an overglasses version were made available, at least for the general consumer release.
Personally, what I crave is a sub-500g laptop replacement for working on the move. To me, Glass’s key innovation is that it obviates the need for a large (and heavy) physical screen, producing similar results for users through projection. I hope that eventually, as batteries become lighter, Google will release an overglasses model with:
- much bigger screen (as seen by users) – particularly for those of us with ageing eyes
- different design, hinged so that the screen can be moved into the middle of the user’s vision (much easier viewing than up/right) when desired, and moved back to the side when not. That would enable users to read War & Peace comfortably on Glass – some would want to!
- support for fast input via a full-size (but light) keyboard – whether portable Bluetooth or virtual keyboard using (not heavy) bracelets/rings
- apps for reading and annotating PDFs, ebooks and other documents – and ideally writing/editing them too, eg Office for Glass? (in combination with full keyboard support, of course)
- much longer battery life, and a processor/apps suited to extended continuous use, and
- full disk encryption enabled by default, at least when you set a lock pattern.
The above represents my own wishlist, but there are other use cases. A friend who’s a keen bird ringer would love to have a voice-activated, voice-output, wearable computer with the BTO app, so that while your hands are occupied handling a bird you could say “Fieldfare” and the computer would say and display “Fieldfare: Full grown ring C, Pulli ring C”, giving you the info hands-free - and ideally you should be able to scroll via voice alone too.
In terms of possible "legal" uses for Glass, Neil Brown has suggested a few:
- Simultaneous translation of foreign language documents: as you are looking at a document, Google Glass converts the particular paragraph to your preferred language — perhaps enough for getting a gist of something, if tuned with a legal dictionary.
- But this isn't possible yet – Word Lens is excellent, however it only works on quite large text, ie on signs. Hopefully in future the camera and app will both improve enough to make this possible.
- As you read through a document, it captures the text, OCRs it, and turns it into a file for you to edit — perhaps even "dictating" notes as you read, which are then appended to that digital file for subsequent incorporation.
- Again, if only! This expands in more detail on my own document reading/annotation wishlist item. OCR seems dependent on camera quality and app availability, especially as they would have to cater for any unsteady hands holding a document, and as previously mentioned an audio note transcription app isn't yet available (which would need more fine-grained error correction than "start all over again" if one word is transcribed wrongly).
- Advocates in court, so that others can "pass notes" to them without having to shove pieces of paper around.
- Yes, this is possible by sending an email or text to the advocate. It would be great if you could quickly put Glass into "restricted mode" in court, a kind of filter that lets through only important messages from (pre-defined, editable) contacts or groups of contacts, to prevent too many distractions in court or indeed meetings – then disable restricted mode again when you're out. It would be interesting to see if courts ban Glass, even for open sessions.
- A presenter's notes available to them on a per-slide basis, just a quick glance away; no more need for shuffling papers in the hand, or looking down to a screen on the floor, tying you to one place on the stage. Or even just the "next build" for the current slide — moving the presenter view right into the presenter's view.
- Again, not possible yet, see my wishlist item on "Office for Glass" – but hopefully one day!
15. More info
- Metadata saved with Glass photos.
- Quick start guide including “Getting started” video
- Community forum
- Social media queries: #askanexplorer
- Photos taken with Glass, on social media: #throughglass (there's one full example on this page)
- Glass Help
- Glass FAQ: including when using a jackhammer or scuba diving! (hint: not a good idea with Glass…)
16. VerdictAs Google makes very clear, Glass is still in beta. Developers with an eye to the future of computing will certainly want, indeed need, one. As for everyone else, those earning below partner/professor/“head of” levels might understandably balk at paying £1000 for a beta product, unless of a pioneering bent or won over by the cool factor.
Personally, I’d happily buy one even at that price – but only if and when my wishlist features are incorporated, because a laptop replacement is my own ideal use case for Glass, and yes I’d don bracelets and not care how it looked! Until then, I’d consider Glass should the price be significantly reduced, but it’s probably of most benefit to Now and Plus users, and I’m not big on either. So, for the features Glass currently offers, my smartphone is good enough for me, for now.
Info in this review was gleaned from quizzing Google staff at the demo, at Glass's London developers’ launch or from Google’s website. Some graphics are from Google’s site, used with Google's kind permission. Many thanks to the Googlers for their patient answers, which were of course to support the demo and are in no way official Google statements! This review is written in my personal capacity only.
© W Kuan Hon, 2014. This review may be copied/redistributed under a Creative Commons CC-BY-NC 2.0 UK licence, attributing Kuan kuan0.com and linking to this review ie http://blog.kuan0.com/2014/08/google-glass-review-photos-pics.html.
 Sometimes, somewhat unfortunately, known as“Glassholes”. So much so that Google released an etiquette guide of dos and don’ts for Explorers… including don’t “be creepy or rude”!
 Which Google calls Basecamp, but I’m tempted to call a Glass House.
 Not “surrender forever”. Not daft, me.
 Some patent diagrams have been posted.
 Helpful graphic on the science http://www.tagseoblog.com/how-google-glass-works-infographic
 Google asked me not to disclose the address, so no amount of coercion or bribery will get me to reveal it, no sirree.
 Including reports that disabling Google+ from Glassware didn’t work, and that Glass uploaded a private album from a paired iPhone! It seems the best if long-winded solution is to disconnect Glass from your phone and wifi, snap your “private pictures”, transfer them to a computer via the USB cable, delete them from Glass, then re-enable Glass connectivity…
 Could prove very expensive if you need more than one pair like me, but hopefully few people have eyesight as bad as mine. Disposable contacts aren’t available in a high enough prescription for my tiny bulgy eyes.
 “Glass is designed for micro-interactions, not for staring into the screen, watching Friday night movie marathons or reading "War and Peace."”
 The previous link says that Glass locks only on turning Glass off – but fully powering down isn't the same as just putting it to sleep, strictly. However, Google assured me that after pressing the power button once to deactivate it also locks it.
 Glass wouldn’t stay in place without my holding it over my specs. I can’t see without prescription lenses, and multiple prescription frames would be too expensive for me!
 Personally I’d have to buy another 2 frames just to use Glass. Were an overglasses version available, one unit would be all I’d need.
 Yes, I meant sub-500g. Sub-1 kg is still too heavy if you’re short, feeble, unfit – and/or have back problems. Teenagers, kids and some women would relish full computers weighing under 500g; even some men have bad backs.
 And even further in the future, get the screen to move into the centre automatically with a voice command, and out again with another!
Plus, ditto – Google recently backpedalled on its initial insistence on real names, but did so too late for me. If it had allowed pseudonyms from the outset I would have tried it and maybe even moved on to using it with my real name, but currently I don’t have the time/energy/braincells to make the effort.
Tuesday, 19 August 2014
And here's a photo of a display case in the London Glass showroom (Basecamp, which I call a Glass House!):
Plus (with permission) a photo taken using Glass itself - click on the image for the full-sized version:
Wednesday, 23 April 2014
The UK government just updated their (alpha) cloud security principles guidance, first issued in Dec 2013.
- intro to cloud security guidance - aims etc
- detailed guidance on implementing the cloud security principles.
As they didn't provide a markup or redline (maybe next time?), below is a basic (text-only) comparison of the changes made to the Dec 2013 version of the UK government cloud security principles. Some of the deleted text has been moved to the implementation guidance.
Service Security Principles Published 19 December 2013
Data in transit protection
Asset protection and resilience
Separation between consumers
Supply chain security
Secure consumer management
Secure on-boarding and off-boarding Service interface protection
Secure service administration
Audit information provision to
Secure use of the service by the consumer
This document describes principles which should be considered when evaluating the security features of cloud services. Some cloud services will provide all of the security principles, while others only a subset. It is for the consumer of the service to decide which of the security principles are important to them in the context of how they expect to use the service.
Some service providers will be able to offer higher levels of confidence in how they implement the different security principles. Consumers will need to decide how much, if any, assurance they require in the different security principles which matter to them.
These principles apply equally to Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS) as defined by NIST.
1. Data in transit protection
The confidentiality and integrity of data should be adequately protected whilst in transit. The following aspects should be specifically considered: Consumer to service Within the service (for example, between data centres)
2. Asset protection and resilience
Data should be physically secure as it is processed by and stored within the service. This security should be based on suitable physical security controls within data processing, storage and management locations. The business requirements for availability of the service should be an important consideration when choosing a cloud service. The consumer should ensure that a contractual agreement is in place with the service provider which adequately supports their business needs for availability of the service. The legal jurisdiction of the service will be an important consideration for many consumers, especially if they wish to use the service to store or process personal data. This principle depends on the physical locations of processing, storage, transit and management of the service. The following aspects should be specifically considered: Location of data centres hosting the service Security surrounding those data centres Location of service management facilities How the confidentiality and integrity of data-at-rest will be maintained Availability of the service
3. Separation between consumers
Separation between different consumers of a service
should be achieved at all points within the service, including across compute, storage and networking resources. An important consideration will be whether the service is a public, private, or community, shared cloud service; if all tenants of the service are known to be trustworthy then less confidence in the separation properties of the service may be acceptable.
The service provider should have a security governance framework that coordinates and directs their overall approach to the management of
IT systems, services and information. A clearly identified, and named, senior executive should be responsible for security of the cloud service.
5. Operational security
The service provider should have processes and procedures in place to ensure the operational security of the service.
The following aspects should be specifically considered: Configuration and change management Vulnerability management Protective monitoring Incident management
6. Personnel security
Service provider staff should be subjected to adequate personnel security screening
for their role. At a minimum this should include identity, unspent criminal convictions, and right to work checks. For roles with a higher level of service access, the service provider should undertake and maintain appropriate additional personnel security checks.
7. Secure development
The service should be developed in a secure fashion and should evolve to mitigate new threats as they emerge.
8. Supply chain security
Cloud services often rely upon third party services. Those third parties can have an impact on the overall security of the services. The service provider should ensure that its supply chain satisfactorily supports all of the security principles that the service claims to deliver.
9. Secure consumer management
Consumers should be provided the tools
they need to securely manage their usage of the service. The following aspects should be specifically considered: Authentication of consumers to management interfaces Separation of consumers within management interfaces Authentication of consumers within support channels Separation of consumers within support channels
Secure on-boarding and off-boarding The service should be provisioned to consumers in a known good state, and their data must be satisfactorily deleted when they leave the service. When physical storage components reach their end of life, the service provider should make appropriate arrangements to securely destroy or purge any consumer data they held.
Service interface protection
All external or less trusted interfaces of the service should be identified and have appropriate protections to defend against attacks through them.
The following aspects should be specifically considered: Connections to external services on which the service depends Dedicated connections to tenants Remote access by service provider Publicly exposed services
12. Secure service administration
The methods used by the service provider’s administrators to manage the operational service
(monitor system health, apply patches, update configuration etc.) should be designed to mitigate any risk of exploitation which could undermine the security of the service. The security of the networks and devices used to perform this function should be specifically considered.
13. Audit information provision to
Consumers should be provided with the audit records they need
in order to monitor access to their service and the data held within it.
14. Secure use of the service by the consumer
will have certain responsibilities when using the service in order for their use of it to remain secure, and for their data to be adequately protected. Depending on the type of service, the consumer will have responsibilities relating to the following topics: Audit and monitoring Storage Networking Authentication Development security End user devices used to access the service Secure configuration of the service Patching 15. Glossary Management interface a service exposed to consumers or service provider administrators to allow administrative tasks to be performed. Support channel an online, or out of band (e.g. telephone), communication channel which consumers can use to obtain support from the service provider. On-boarding the process of a consumer moving on to the service. Off-boarding the process of migrating a consumer away from a service. Public, private and community cloud refer to the NIST definitions of these terms. Consumer a tenant of the cloud service.
Sunday, 13 April 2014
What's the difference between IaaS, PaaS and SaaS? There still seems to be confusion especially about PaaS. I hope this will help.
Consider what lies behind using a software application, like email. (I will be simplifying and generalising below, to get the point across, so no need to point out eg that some languages are interpreted, that some programs can be run directly without installation, and that PaaS applications may need to be coded to integrate with the specific PaaS provider’s libraries!).
- The application is coded – someone writes the application in a programming language like C++, Python etc.
- The application is compiled – the code is converted into a form that can be run on a particular operating system eg Windows, Mac, Linux, Android, iPhone (iOS) etc.
- The application is acquired – eg downloaded from a website, obtained on DVD.
- The application is installed on the operating system – eg doubleclicking an .msi file in Windows.
- The application is run and used by the user – eg doubleclicking on the program filename.
Non-cloud – the end user of the application typically only takes steps 3-5, or even just 5 on a corporate network where the IT department has already taken care of 3 and 4.
SaaS – the cloud user only takes step 5, typically by logging into the SaaS service over the Internet (or company network) to access the application, instead of clicking on a local program name; the SaaS provider takes care of all the rest.
IaaS – the cloud user must take care of ALL of steps 1-5. In addition (consider this a step 3.5!) it must also manage its own VMs including creating VMs and installing the operating systems on its VMs (though it can use snapshots). But it could use someone else’s code (eg open source software) rather than writing the code itself (in which case it skips step 3). Or it could use someone else’s application, go straight to step 3 and install the application in its cloud VM on top of the operating system it installed, assuming the application licence allows installations in VMs. In step 5 the individual end users could be the employees of the cloud user organisation, or its customers, or both.
PaaS – the cloud user only takes care of step 1, again writing its own code (normally using an SDK or software development kit downloadable from the provider) or obtaining code from elsewhere. The PaaS provider handles steps 2-4. Step 1 can be and is often done locally, then the code is uploaded to the PaaS provider. Again, in step 5 the end users could be employees of the cloud user organisation or its customers. Hence startups offering new services over the web, eg mobile applications, like using IaaS or PaaS because they don’t have to buy equipment to service their customers, they can just focus on running their systems (in IaaS) and coding (in both). With PaaS, they don’t even have to manage IT systems - they can concentrate just on coding. Hence the ‘platform’ in PaaS – it provides a ‘platform’ for PaaS users to code their applications, deploy their applications (to servers provided by the PaaS provider) and host their applications (on servers provided by the PaaS provider), so that the applications are available for use by their end users over the Internet or corporate network.
Wednesday, 12 February 2014
Here are my 9 Ds of Cloud Computing - D for Differences (which I produced for my Information Security FS 2013 presentation).
Cloud computing is a form of sourcing / outsourcing, of IT resources. But -
- Disassociation - separation of the physical from the logical is common (eg physical access to data vs logical, often remote, access); and so is separation of ownership vs control vs use
- Diverse supply chain (hardware, software, services); even layers of services are possible, eg:
- Don’t always know or have influence over all suppliers - customers are in quite a different position from traditional outsourcing, it's often a 'cloud of unknowing' for customers, who may not always be able to find out full information about sub-providers etc, or be able to negotiate providers' standard contract terms
- ‘Direction of travel’ is reversed - if using sub-providers. In traditional outsourcing, a customer may go out to tender with details of the service it seeks, discuss the position with several shortlisted potential providers and narrow it down; the provider finds sub-contractors to help it deliver the service requested by the customer. In cloud, SaaS (or even PaaS) providers often build their services on top of pre-existing IaaS or PaaS services, then offer their services to customers, ie the 'direction of travel' is the opposite from that in traditional outsourcing; and opportunities for customising the service are limited
- DIY - cloud involves the self-service use by customers of IT hardware / software infrastructure, offered as services, such as software applications in SaaS or virtual servers in IaaS; the provider doesn't actively process data for customers
- Design – the design of the individual service (as well as user measures eg encryption, which the service may or may not facilitate) will affect the extent to which the provider has access to user data, including encrypted data. Key access is also critical - if the user has encrypted the data but the provider can access the key, it can still access intelligible data. Conversely if the provider has encrypted user data and manages the key securely, any sub-provider(s) may not be able to access intelligible user data.
- Data – cloud-processed data are often:
- distributed, which overlaps with the following, that cloud data may be
- divided into chunks / fragments which are stored, and sometimes processed, separately
- duplicated (multiple replicas or copies of data may be taken, perhaps to different geographical locations, for backup/business continuity purposes),
- 'deleted' in different ways - deletion may only delete 'pointers' to data rather than scrubbing underlying data, which are gradually over-written over time; even any scrubbing of data may be achieved to different degrees of deletion (and security), and duplicates of data stored in backups, etc may not get deleted
- Dependence – on shared, third party resources - including the customer's Internet connectivity
- Degrees of control, eg regarding security issues, differ with the situation - it's not one size fits all (see table below)
Table © Cloud Security Alliance reproduced with permission
See also: previous post about the 12 Cs of Cloud Computing (here's the full SCL article: The 12 Cs of Cloud Computing: A Culinary Confection), including explanations of SaaS, PaaS and IaaS for those not familiar with the terms.