Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Attacking Developers Using 'Shadow Containers'
Threaded  |  Newest First  |  Oldest First
alphaa10
50%
50%
alphaa10,
User Rank: Strategist
2/1/2018 | 10:20:15 AM
Interviews Need Editing
Potential interest in every video segment. However, every interview needs editing-- video or audio-- because, without editing, it becomes a prisoner of its own format, laden with vague questions, obscure, hard to follow answers, and general tedium. With all due respect, the current video interview format rarely meets expectations.

A tighter delivery of information is accomplished with prerecorded video of text and graphics (where appropriate). Data professionals have learned to take in information at a much higher rate, and the exclusively text/graphics approach is likely to make the information flow "denser" or faster. As a prepared presentation, the information also can be more clearly focused and organized.

Another suggestion is to have the interviewer come from a background in the area under discussion. Unfocused questions like, "What are you fondest memories of the Black Hats of years past?" are innocently but agonizingly general, and serve only to open segments, as if trying to make conversation. DR should explore the utility of having veterans of the field as interviewers, with a general script to keep the line of questions integrated.

Potentially, of course, video interviews open something really fascinating, but we rarely find somebody with a good story just waiting to be interviewed, try as we might to prime interviewees with advance questions.

Let's face it-- in most situations, people have a tendency to make video resemble an exercise in filling a time slot. Truthfully, this is the first and last time I plan to watch a DR Black Hat video in the current format-- I simply don't have the time. In return for your having invested so much effort in production, not to mention actual interview time, you would serve your own cause by spendnig additional time editing the result.

You cannot afford to omit more intensive post-production, because only quality gathers an audience. Our time, like yours, is valuable-- please, make our investment even more engaging. That said, the UBM effort shows promise-- few other publishers take the trouble to cover these areas with such [potential) depth and detail.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.