If You've Done Nothing Wrong, You've Got Nothing to Fear
So we're told. But it didn't work for Jacqui Smith.
If you tell enough stories, perhaps the moral will show up.
So we're told. But it didn't work for Jacqui Smith.
at
17:54
0
comments
That's bad.
I'm seeing Acai Berry among other approaches to the size of my waist and a renewed emphasis on the size and stiffness of my male member. There are fewer fake watches -- the SS Submariner -- and a very few swine flu.
at
21:48
0
comments
Labels: spam
I'm not interested in concealing my identity, exactly, but I don't put my real name on these because any security writing that uses real-life examples will sometimes be about Fail, even if it's Fail rectified, and who wants to go public about their own employer's Fail?
Even so, I've always been circumspect about what I say because I've felt that the intersection of the things I talk about -- Kent, Finance, Computer Security, Old man -- is going to be a pretty sparse set. Anyone who cares could find out who I am.
So it's interesting to see Schneier blogging about some research from PARC. Apparently the end-points of a regular commute are sufficient to identify a huge proportion of people. Pretty much all that required is that the granularity is fine enough for people to be working in a different zip, county or whatever from the one they live in.
I'll be more careful in future. I have a plan.
at
22:19
0
comments
Labels: investigation, PID, privacy
Went to pick up my printout from the printer and there it was: The biggest secret in the firm, and one from which I am firmly excluded. Ninety colour pages which someone had collected, collated and left prominently displayed to be picked up.
A few minutes in the event log of the print server gave the answer -- the same document printed twice in succession: the signature of a user losing track of what they've done. He's back on track now.
The report had been out on display for thirty minutes when I found it. I imagine the person who tidied it up will be one of the three people who used that printer between me and the inadvertent leak. But who else saw it is much harder to tell.
at
21:33
0
comments
Labels: investigation, story
ContactPoint, the government list of children, is live today in test areas. When it's complete, it will hold contact details for every child in the UK, with a NIN and a list of the agencies dealing with the subject.
The rights and wrongs of this are one thing, but there's a gap at the heart of the published security policy (pdf) -- they've left one point out, and it's the hard part that makes the rest work.
They're proud of the access control -- it'll be two factor and the web access won't work from just anywhere (I hope it'll be limited to registered IP addresses). Users will need to be in a role that requires access and have passed CRB checks.
But it fails, it misses the point. Apparently the designers expect there will be three hundred thousand users across the NHS, education authorities, LA social work departments, the police, courts and probation service. It seems on the low side, but just that number gives us around a thousand retirements a month. Add in all the role changes where users no longer need the access, or change employer or reporting line enough to change the origin of their entitlement and I call that around five thousand leaver events a month.
No-doubt ContactPoint has the staff to do it, but however will they hear about the leavers? We have enough difficulty finding the leavers in a few hundred users, and we have access to the payroll. It looks as though ContactPoint is going to be dependent on users or managers volunteering that they no-longer need the acccess. With all the good will in the world -- and social work departments are often very replete with ill-will -- that's never going to be anyone's top priority.
I'm not surprised they left it out. I wonder when it's going to bite.
at
22:00
0
comments
Big current spam trick: The stolen webmail account.
Hotmail etc. make it hard to register accounts for spamming, so a lot of mail out of their relays isn't spam. And that means that spam detectors mod up mail coming through those gateways -- if it's truly from Hotmail, it's much less likely to be spam. So we're seeing a resurgence -- it feels like 1998 -- of spam from public webmail services. Examined, it turns out:
I wrote about this, from the other side, last year. But this is more sophisticated, going to big lists, not just address books.
Just another penalty of being spywared.
at
18:56
0
comments
But it was 1300 earlier in the month.
There's a big new botnet at work -- quarantines at have vastly increased lately. Mostly traditional stuff with rather more images and spam poetry than we've seen lately.
One thing that stands out is the new wonder drug: Magnesium Oxide. Why am I getting Magnesium Oxide spam? It's milk of magnesia -- an antacid. Why would anyone buy that online? What really perplexes me is that they obviously expect their target market to know why they want it -- or is it that people who respond to spam are precisely the people who will buy anything?
at
21:17
0
comments
Labels: spam
(Two FSA posts in two days -- bad sign.)
The FSA have lately been taking a very hard line on data leak risk, and they themselves deal with extremely sensitive information.
So it does seem rather hard that they can't accept or originate TLS encrypted email. It's doubly hard that they use Messagelabs which handles TLS easily -- encryption must have been explicitly disabled.
So I have to dick around with fancy encryption utilities to get something that should be free.
at
21:11
0
comments
Just a little note about our pandemic planning.
When the system was set up, we canvassed the business very carefully. Who could work at home, and who would have to come in?
The message was clear. Investors and traders could not work at home. They needed their colleagues around them, they needed their morning meetings and their bosses and compliance reps needed to see them. Delivering the order management and dealing apps on the pandemic remote access system was unnecessary and actually dangerous. Fortunate really, as some of them do not respond well to Citrix.
Well, now here we are, and I sense a slight quavering of the upper lip. When you really think about it, the idea of wealthy, numerate, well-informed and self-confident men and women with family responsibilities actually risking a lethal infection to nurse their portfolio is a bit daft. They'll stay home whatever the boss says. The first two or three, you can sack, but if it's the whole team, it becomes our problem not theirs.
Meeting tomorrow to start the the process -- "well, if that's not what you really meant, what do you mean?" We'll see how it goes.
Meanwhile, Mrs U is discussing what food to stock-pile.
at
21:24
0
comments
The protestors -- G20 Meltdown and the climate campers -- did a big favour to London finance firms.
For three years, the FSA has been nudging us to do "pandemic planning" -- to prepare for situations like a legal or de facto quarantine where most staff will be staying at home by choice or under legal compulsion (or a train strike, or civil disorder or ...) This isn't DR proper -- if you don't want to say pandemic (and I don't, it's silly) you can call it Colleague Availability Planning.
And since we are a good and dutiful regulatee we have done what we can. In our case, that's a Citrix farm and an SSL VPN, with security settings that make it a little less unsafe when it's accessed from untrusted PCs. To ensure it's running and up to date, we use it for most of our remote access (I've preserved a little dignity by insisting that remote admins, and staff who need off-line access to data still have to use a trusted laptop.) The gimmick is that the equipment is grossly overspecified. Over a normal day, maybe 2% of staff log on. But the farm, the gateways and the Internet access is sized for 50%, and that presented us with a problem. We have no idea whether it is could handle the planned load, as we could never arrange that many to try it at once.
We got some information from the snow day in February -- that got us up to 15%. But the G20 demos were another thing again. Staff told to work at home, and pretty much told that unless they showed up on the VPN they'd be taking the day as holiday.
The first day, we struggled. A lot of silly glitches and one big one -- the presentation servers in the farm had not been built to specification. Very easy to fix, as it happened, and the second day went smoothly with about 40% of users -- pretty much the expected number -- on line.
And that's the gift that the G20 protesters gave us. Whatever you think of Mexican Swine Flu, you can be certain that we'll have to demonstrate to the FSA that our pandemic plan is up to scratch. And, now, thanks to the crusties, we can say, confidently and truthfully (and you need both to speak to the FSA) that it is.
Thanks, guys and gals! Was that what you wanted to do for us?
at
21:09
0
comments
Naked-eye planets, obviously.
To be honest, I never expected to see Mercury. It's much harder to spot than Jupiter, Mars, Venus and Saturn. And I haven't seen Saturn, confidently, for a while.
When I went out to shut up the chickens at 21 my eye was captured by the one of the prettiest new moons I've seen. A tiny crescent silver sliver reclining, cradling a huge oval of earthlight in the last purple of the sunset. And there it was -- just off the moon/sun line -- the only star visible between the moon and the horizon.
I'd been tipped off by the night sky column in the LMS's BBC Focus magazine. "Surprisingly bright" it said and bright enough it was. And that's my lot. If I want to see another planet, I'll need binoculars. But the LMS is off too a good start.
at
22:46
0
comments
This is mostly a funny story. "Now, boys, you are getting F grades at school for the exact same reason that you probably shouldn't bother trying to hack into the systems to change them..... "
Perhaps it's wrong to laugh. The Sumitomo hackers were prosecuted with evidence gathered by the spyware they left behind. Keyloggers are two-edged swords.
at
19:10
0
comments
Labels: investigation
This is an interesting story on the BBC. It appears that as part of their probation, a pilot sample of convicted sex offenders are to be interviewed under a polygraph in an attempt to catch them sliding back into abusive behaviour.
I don't think any official body in the UK, certainly not the courts, police or the probation service are prepared to say that lie detectors "work" -- in the sense that they reliably detect when an interrogation subject is lying. The problems seem to be:
"Disclosures made during polygraph examinations, as well as conclusions drawn from passed or failed examinations, allow probation officers and the police to intervene to reduce risk ... Just as important, it is also aimed at enhancing the co-operation of offenders with supervision, helping them to focus on, and avoid, the sorts of behaviours that make re-offending more likely."That is a very careful statement indeed, and I hope the Beeb haven't picked out something unrepresentative. Grubin is a proper academic at a proper university -- Newcastle -- where the university profile identifies his current approaches to sex-offenders as being polygraphy and Prozac. And on the strength of this quote, it seems that he finds the chief value of a lie detector is that it's called a "lie detector". He does mention passes and failures, but his focus is on the interview itself. It appears that the purpose of the "lie detector" is not to spot lies, but to persuade the subject that telling the truth is the best plan.
at
21:41
0
comments
On the theory that risks need names, here's a couple more from the recent Sumitomo bank job.
at
21:37
0
comments
at
19:50
0
comments
Labels: spam