Friday, December 5, 2014

Week 14: Security, Privacy, and Cloud Computing

1. O'Harrow, R. (2005). Chapter 10. In No Place to Hide: Behind the Scenes of Our Emerging Surveillance Society (281-300). New York: Free Press.

  • electronic surveillance: future of data collection
  • transit cards monitor traffic, travel activity
  • hand readers @ workplaces instead of traditional punch cards
  • GPS, CCTV
  • tollbooths as security points
    • e-toll credits to verify location
  •  RFID (radio frequency id) @ heart of system
    • "virtual borders"
  • "why worry if you have nothing to hide"? --> awkward logic?
  • surveillance as defense/security ---> but v. what/who?

2. Jaeger, P., Lin, J., Grimes, J., & Simmons, S. (2009). Where is the cloud? Geography, economics, environment, and jurisdiction in cloud computing. First Monday, 14(5). http://firstmonday.org/ojs/index.php/fm/article/view/2456/2171

3. Library Data in the Cloud - National Information Standards Organization. (n.d.). Retrieved November 21, 2014, from http://www.niso.org/news/events/2014/virtual/data_in_the_cloud/

4.  Cloud Computing Online Training. (2014, Mar 3) Learning Cloud Computing With Amazon Web Services What Is The Cloud. Retrieved from https://www.youtube.com/watch?v=Neys3rci14o

  • cloud computing: large data centers with enough dynamism to make scalable for users
    • functionality depends on size and continuity:
    • efficient flow of data
  • although not familiar w/ term or unaware of own use, many ppl already involved in it
    • ex. Gmail, Flickr
  • "cloud" not just physical machines
    • also raises policy issues
  •  diff components
    • infrastructure
      • computational resources
      • storage
      • ex. Amazon Elastic Compute Cloud
    • platform
      • software stack
      • ex. Google App Engine
    • application
      • Web services running on top of cloud computing component


What is...?
  • cloud computing offers possible solutions to "Web-scale" challenges in processing data
  • commercialization of "utility computing" services and development
    • addtl revenues
    • consolidation: overall reduced costs
  • liberates users from maintaining infrastructure


Who uses...?
  • app hosting
    • cloud provider w/ maintenance tasks
  • batch processing
    • large amt of data
  • temporary use x existing IT infrastructure, aka cloud bursting
    • temporary/seasonal peaks
  • user data + apps in cloud cluster
    • owned and maintained by provider
    • legal issues?


Where is...?
  • centralization of info + countless computing resources
  • location of data centers a major issue: possibility of portable dc?
    • suitable physical space (at least warehouse-sized)
    • near high-capacity Internet connections
    • lots of affordable electricity/other energy resources
    • laws of jurisdiction 
      • adjudication of cases?
      • govt intervention?
      • costs

Rules and policies
  • users expect reliable, high-speed 24/7 access
  • also secure and private connections
  • liability + intellectual property + ownership of data
  • easy transfer of data
  • for corporations: ability to be audited

Week 12: Muddiest points

1. I'm familiar with the concept of folksonomy as an active user of the photo-sharing site Flickr, but I'm wondering how extensive the use is as a supplement to the controlled vocabulary provided by other institutions, or whether adoption of what was before a folksonomic term depends on the frequency/popularity of that term.