Last year, I was invited to contribute a paper to a special edition of the Health and Technology Journal published by Springer/Nature. The special issue addressed privacy and security, with a particular focus on healthcare and medical data. I’m happy to announce that now, for four weeks only, the publishers have made the whole issue available free.
From our accompanying blog post last July:
“The paper, “Trust and ethical data handling in the healthcare context” examines the issues associated with healthcare data in terms of ethics, privacy, and trust, and makes recommendations about what we, as individuals, should ask for and expect from the organisations we entrust with our most sensitive personal data.”
Although we can find several comprehensive and mature data protection frameworks around the world, current legal safeguards to not seem to prevent data controllers from indulging in:
In my paper, I argue that a narrow focus on regulatory compliance can lead to a “checklist” mentality, obscure the real reasons why organisations should treat data with care and respect, and lead to poor outcomes for both the organisation and the individual. I Continue reading
In part 1 of our series on the basics of Linux, we learned how to download Linux, whether you should use the CLI or the GUI, how to get a SSH client, how to login to Linux, and how to get help.
In part 2 of our series, we learned how to know what type of Linux you are using and how to navigate the Linux file system.
In this final post in the series, you’ll learn about Linux files, Linux permissions, Linux package management, and how to install applications in Linux.
Let’s say that a user named “david” was denied access to the file /var/log/syslog. The reason for that is likely the user “david” doesn’t have permission to access to the file.
You can see this if you execute ls -l /var/log/syslog:
david@debian:~$ ls -l /var/log/syslog
-rw-r----- 1 root adm 9074 May 15 10:17 /var/log/syslog
The file is owned by the user “root” and the group “adm”. The file permissions are “rw” (shorthand for read/write) for the owner and “r” (shorthand for “read”) for the group with no permissions for anyone else. The graphic below shows how file permissions work in Linux.
In the file permissions Continue reading
50 percent of central offices will have CORD by 2023.
Extreme Networks demonstrates network automation via Workflow Composer and StackStorm at Network Field Day 17.
The post BiB 26: Extreme Networks At NFD17 – Composing Workflows For Mean Time To Payrise appeared first on Packet Pushers.
Can he move the company beyond private cloud?
I’m often asked what the trick is to become a smarter person—there are many answers, of course, which I mention in this video. But there is “one weird trick” many people don’t think about, which I focus on here.
Chronicle will use machine learning to help enterprises manage their data.
A new application tracks a number of user and device behaviors to identify attackers.
Effective January 23, 2018 Cisco will be incorporating a new version of its CCIE Collaboration exam blueprint into both the written and lab exams. Those who are scheduled to take the CCIE Collaboration exam prior to this date will not be affected by the blueprint change.
For those who are scheduled to take the CCIE Collaboration exam on or after July 23, 2018 here are the major changes you can expect to see:
The v2.0 CCIE Collaboration exam will be split into 8 domains unifying the written and lab exam topics. What this means is that instead of having 9 domains in the written exam and 7 in the lab exam, candidates will be tested on topics in only 8 domains total across both exams. In version 2.0 of the CCIE Collaboration exam, instructions will explicitly state which domains pertain to which exam, and the relative weight of each domain.
Topics Added in v2.0:
The entire cloud native ecosystem has begun to address enterprise needs.
In advance of Data Privacy & Protection Day, the Online Trust Alliance, an Internet Society initiative, just released the Cyber Incident & Breach Trends Report (press release here), a look back at the cyber incident trends in 2017 and what can be done to address them. This report marks the tenth year OTA has provided guidance in this area, and while the specifics have certainly changed over time, the core principles have not.
Originally we just looked at the number of reported breaches, but last year we broadened the definition to “cyber incidents,” which includes ransomware infections, business email compromise (BEC), distributed denial-of-service (DDoS) attacks and infiltrations caused by connected devices. This broader definition paints a more realistic picture of the threats and associated impact facing organizations today.
This year we found that the number of cyber incidents nearly doubled to 159,700 globally, and given that most incidents are not reported, this number could easily exceed 350,000. This is more than 30 times the number of breaches alone, so provides a very different perspective on the threat landscape. As in previous years we also assessed the “avoidability” of breaches by analyzing their cause and found that 93% were avoidable, Continue reading