<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.pentestpartners.com/security-blog/alarm-systems-alarmingly-insecure-oh-the-irony/"/>
	<rdf:li rdf:resource="https://twitter.com/internetofshit/status/739895587282288640"/>
	<rdf:li rdf:resource="http://humanisticsystems.com/2015/10/16/fit-for-purpose-questions-about-alarm-system-design-from-theory-and-practice/"/>
	<rdf:li rdf:resource="http://fractio.nl/2014/08/26/cardiac-alarms-and-ops/"/>
	<rdf:li rdf:resource="https://logentries.com/logentries-announces-machine-learning-analytics-for-ops-monitoring-real-time-alerting/"/>
	<rdf:li rdf:resource="http://go.boundary.com/10freeserversprereg"/>
	<rdf:li rdf:resource="https://deadmanssnitch.com/"/>
	<rdf:li rdf:resource="http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877"/>
	<rdf:li rdf:resource="http://www.techspot.com/news/40946-iphone-users-not-waking-up-on-time-due-to-dst-bug.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.pentestpartners.com/security-blog/alarm-systems-alarmingly-insecure-oh-the-irony/">
    <title>Alarm systems alarmingly insecure. Oh the irony | Pen Test Partners</title>
    <dc:date>2017-10-18T21:35:30+00:00</dc:date>
    <link>https://www.pentestpartners.com/security-blog/alarm-systems-alarmingly-insecure-oh-the-irony/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Some absolutely abysmal security practices used in off-the-shelf self-installed wireless home alarm systems -- specifically the Yale HSA6400.  Simple replay attacks of the unlock PIN message, for instance

]]></description>
<dc:subject>security home wireless alarms yale fail</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:48703cbc916e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wireless"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yale"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/internetofshit/status/739895587282288640">
    <title>The Mitsubishi Outlander vulnerability allows trivial remote car alarm unlocking.</title>
    <dc:date>2016-06-07T12:03:44+00:00</dc:date>
    <link>https://twitter.com/internetofshit/status/739895587282288640</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Nearly-open wifi (easily-cracked weak WPA PSK), and a 6-byte string to disable the car alarm, discovered via replay attack.  Massive fail]]></description>
<dc:subject>internetofshit mitsubishi fail outlander wpa alarms security replay-attack</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:43f14132fcad/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internetofshit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mitsubishi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:outlander"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wpa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:replay-attack"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://humanisticsystems.com/2015/10/16/fit-for-purpose-questions-about-alarm-system-design-from-theory-and-practice/">
    <title>Alarm design: From nuclear power to WebOps</title>
    <dc:date>2015-11-11T17:31:02+00:00</dc:date>
    <link>http://humanisticsystems.com/2015/10/16/fit-for-purpose-questions-about-alarm-system-design-from-theory-and-practice/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Imagine you are an operator in a nuclear power control room. An accident has started to unfold. During the first few minutes, more than 100 alarms go off, and there is no system for suppressing the unimportant signals so that you can concentrate on the significant alarms. Information is not presented clearly; for example, although the pressure and temperature within the reactor coolant system are shown, there is no direct indication that the combination of pressure and temperature mean that the cooling water is turning into steam. There are over 50 alarms lit in the control room, and the computer printer registering alarms is running more than 2 hours behind the events.

This was the basic scenario facing the control room operators during the Three Mile Island (TMI) partial nuclear meltdown in 1979. The Report of the President’s Commission stated that, “Overall, little attention had been paid to the interaction between human beings and machines under the rapidly changing and confusing circumstances of an accident” (p. 11). The TMI control room operator on the day, Craig Faust, recalled for the Commission his reaction to the incessant alarms: “I would have liked to have thrown away the alarm panel. It wasn’t giving us any useful information”. It was the first major illustration of the alarm problem, and the accident triggered a flurry of human factors/ergonomics (HF/E) activity.</blockquote>

A familiar topic for this ex-member of the Amazon network monitoring team...]]></description>
<dc:subject>ergonomics human-factors ui ux alarms alerts alerting three-mile-island nuclear-power safety outages ops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1c46b439b712/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ergonomics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:human-factors"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:three-mile-island"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nuclear-power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:outages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fractio.nl/2014/08/26/cardiac-alarms-and-ops/">
    <title>Applying cardiac alarm management techniques to your on-call</title>
    <dc:date>2014-09-01T09:34:20+00:00</dc:date>
    <link>http://fractio.nl/2014/08/26/cardiac-alarms-and-ops/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[An ops-focused take on a recent story about alarm fatigue, and how a Boston hospital dealt with it. When I was in Amazon, many of the teams in our division had a target to reduce false positive pages, with a definite monetary value attached to it, since many teams had "time off in lieu" payments for out-of-hours pages to the on-call staff.  As a result, reducing false-positive pages was reasonably high priority and we dealt with this problem very proactively, with a well-developed sense of how to do so.  It's interesting to see how the outside world is only just starting to look into its amelioration.  (Another benefit of a TOIL policy ;)]]></description>
<dc:subject>ops monitoring sysadmin alerts alarms nagios alarm-fatigue false-positives pages</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:89a98e187218/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nagios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarm-fatigue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:false-positives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pages"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://logentries.com/logentries-announces-machine-learning-analytics-for-ops-monitoring-real-time-alerting/">
    <title>Logentries Announces Machine Learning Analytics for IT Ops Monitoring and Real-time Alerting</title>
    <dc:date>2014-08-25T21:11:15+00:00</dc:date>
    <link>https://logentries.com/logentries-announces-machine-learning-analytics-for-ops-monitoring-real-time-alerting/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This sounds pretty neat:

<blockquote>With Logentries Anomaly Detection, users can:

Set-up real-time alerting based on deviations from important patterns and log events.
Easily customize Anomaly thresholds and compare different time periods.

With Logentries Inactivity Alerting, users can:

Monitor standard, incoming events such as an application heart beat.
Receive real-time alerts based on log inactivity (i.e. receive alerts when something does not occur).</blockquote>

]]></description>
<dc:subject>logging syslog logentries anomaly-detection ops machine-learning inactivity alarms alerting heartbeats</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:19e227cbd18e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:logging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:syslog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:logentries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anomaly-detection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:machine-learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:inactivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:heartbeats"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://go.boundary.com/10freeserversprereg">
    <title>Boundary's new server monitoring free offering</title>
    <dc:date>2014-07-15T09:14:05+00:00</dc:date>
    <link>http://go.boundary.com/10freeserversprereg</link>
    <dc:creator>jm</dc:creator><description><![CDATA['High resolution, 1 second intervals for all metrics; Fluid analytics, drag any graph to any point in time; Smart alarms to cut down on false positives; Embedded graphs and customizable dashboards; Up to 10 servers for free'

Pre-registration is open now. Could be interesting, although the limit of 10 machines is pretty small for any production usage]]></description>
<dc:subject>boundary monitoring network ops metrics alarms tcp ip netstat</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:175d993187e3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:boundary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:network"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tcp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netstat"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://deadmanssnitch.com/">
    <title>Dead Man's Snitch</title>
    <dc:date>2014-04-08T14:05:41+00:00</dc:date>
    <link>https://deadmanssnitch.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>a cron job monitoring tool that keeps an eye on your periodic processes and notifies you when something doesn't happen. Daily backups, monthly emails, or cron jobs you need to monitor? Dead Man's Snitch has you covered. Know immediately when one of these processes doesn't work.</blockquote>

via Marc.]]></description>
<dc:subject>alerts cron monitoring sysadmin ops backups alarms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a15af0101f4f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alerts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877">
    <title>Air France 447 Flight-Data Recorder Transcript - What Really Happened Aboard Air France 447 - Popular Mechanics</title>
    <dc:date>2011-12-08T15:55:06+00:00</dc:date>
    <link>http://www.popularmechanics.com/technology/aviation/crashes/what-really-happened-aboard-air-france-447-6611877</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The (comp.)risks of overautomation strike again. "When trouble suddenly springs up and the computer decides that it can no longer cope—on a dark night, perhaps, in turbulence, far from land -- the humans might find themselves with a very incomplete notion of what's going on. They'll wonder: What instruments are reliable, and which can't be trusted?"]]></description>
<dc:subject>aviation crash flight flying autopilot stalls warnings alarms ui af447 risks automation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cc02b8859dac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aviation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:flying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:autopilot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stalls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:warnings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:af447"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:risks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.techspot.com/news/40946-iphone-users-not-waking-up-on-time-due-to-dst-bug.html">
    <title>iPhone users not waking up on time due to DST bug</title>
    <dc:date>2010-11-02T10:27:31+00:00</dc:date>
    <link>http://www.techspot.com/news/40946-iphone-users-not-waking-up-on-time-due-to-dst-bug.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[lots of people complaining about this on Twitter -- seems the clock changes, but the alarms do not!  Internationali[sz]ation Is Hard]]></description>
<dc:subject>apple iphone alarms dst daylight-savings i18n</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:572cb00ecc56/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:alarms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dst"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:daylight-savings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:i18n"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>