STE WILLIAMS

Demystifying the Dark Web: What You Need to Know

The Dark Web and Deep Web are not the same, neither is fully criminal, and more await in this guide to the Internet’s mysterious corners.PreviousNext

(Image: Kavzov - stock.adobe.com)

(Image: Kavzov – stock.adobe.com)

If you ask the average consumer about the Dark Web, chances are good they won’t have a positive response. Most people assume the Dark Web is malicious – if they know about it at all.

Over the years, and especially of late with breaches and hackers making headlines, the Dark Web’s reputation has been crafted by high-profile arrests and sensational news stories. Films and television shows have also shaped public perception. Even four to five years ago, people within the technology and security industries had a skewed opinion of what the Dark Web is.

“Anyone who was familiar with it typically had an outlandish view of what was happening there,” says Emily Wilson, vice president of research at Terbium Labs. In recent years, the industry has begun to have more developed conversations, discussing how the Dark Web is changing, how it’s responding to different events, and how it fits into their cyber-risk strategies. Employees in the finance and tech spaces, where security is paramount, are especially aware.

Still, she adds, most modern consumers are a few years behind. More have heard of the Dark Web, but those who have are afraid of it. “Their feeling about the Deep and Dark Web is it’s just this bad place,” adds Flashpoint chief strategy officer Chris Camacho.

So what exactly is the Dark Web, and how is it different from the Deep Web? How do they both work, and what goes on there? Here, we hope to fill in the gaps. We spoke with Dark Web experts, who answer your FAQs about the unknown Internet.

 

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance Technology, where she covered financial … View Full BioPreviousNext

Article source: https://www.darkreading.com/risk/demystifying-the-dark-web-what-you-need-to-know/d/d-id/1334681?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Chrome browser pushes SameSite cookie security overhaul

Slowly but steadily, web developers are being given the tools with which to tame the promiscuous and often insecure world of the browser cookie.

The latest big idea is an IETF standard called SameSite (aka RFC6265bis), which Google and Mozilla have promoted since 2016 and the former announced this week it will start pushing more aggressively in Chrome from version 76 this July.

Cookies look simple on the surface – they’re a little chunk of text data that a website can ask your browser to remember, and that your browser will return to that website whenever the browser fetches a page, image or anything else from it. As a security measure, cookies can only be handed over to the domain that set them.

The most common use for cookies is user identification – a site stores an ID in a cookie and the browser returns that ID with each request, so that the site knows who it’s talking to. It’s this simple technique that allows sites to provide authentication and personalisation.

What gives cookies a bad name are third-party cookies, usually put there by advertisers or social media giants as a way of tracking users across sites.

For example, if a user visits a page on example.org with a Facebook button on it, their browser fetches that button from facebook.com as the page is loaded. As with any HTTP interaction, the browser will include any facebook.com cookies in the request to Facebook, along with a referrer header saying what page on example.org the request is coming from.

If you happen to be logged into Facebook (and even sometimes if they aren’t), that request for a button reveals to Facebook who you are, which page you visited and when.

If a social media or advertising company can persuade enough sites to include code hosted on a domain they own, they can turn these cookies into cross-site trackers that build up a map of each user’s behaviour and interests as they browse the web.

And that’s why some users regularly clear them from browser caches or resort to ad blocking or privacy plugins – clunky but effective solutions that can stop sites working correctly.

The consequences of this behaviour aren’t limited to tracking, it can also lead to major security hazards such as Cross-Site Request Forgery (CSRF) attacks.

To simplify, if a user leaves a site (a bank, say) without logging out, in theory it’s possible for a second, malicious, site to fool that user into making unseen requests to the bank that exploit the fact that the user is still logged in.

Perhaps the biggest flaw in this architecture then, is the assumption that just because a browser can hand over a cookie, it should.

How will SameSite help?

Adding SameSite support to Chrome (Firefox, Safari and Edge added experimental support last year) will require web developers to control cookies using the SameSite attribute of the Set-Cookie header, which can be Strict, Lax, or None.

In effect, these are a way of controlling which cookies can be sent by the browser and under what circumstances, doing away with the notion that a browser should send a site a cookie just because it can.

A cookie set to Strict will only be accessible when you’re visiting the domain that set it. If you visit a different site where content from that domain is included, the cookies will not be sent home.

The Strict setting is also a long-overdue way to counter the risk of CSRF attacks.

Alternatively, setting Lax will allow cookies to be made available to third parties via HTTP GET requests, but not by other methods such as POST. This won’t be enough to block a lot of tracking but it will blunt CSRF attacks.

Finally, there’s None, which simply allows a cookie to be accessed in the same way it is today.

Good news for security and, with fewer cookies flying around, privacy too. Cookies will be either same-site and restricted or one of two states of cross-site.

Commented Google’s director of Chrome product management, Ben Galbraith:

It will also enable browsers to provide clear information about which sites are setting these cookies, so users can make informed choices about how their data is used.

Google would also look to limit cross-site cookies where SameSite=None to HTTPS connections as a way of further boosting the privacy effect, he added.

Because Google, unlike many advertising rivals, has little to lose from SameSite (i.e. the popularity of Chrome and Google’s ubiquitous services, including DoubleClick ads), there’s controversy about its intentions.

It’s another example of the internet’s privacy paradox – big tech companies seem happy to promote privacy so long as it doesn’t stop them peeking behind the curtain.

Reforming cookies will also take more than inventing new cookie attributes. Today, most sites set cookies without a SameSite attribute and it will take some time for them to support the new format.

Chrome 76 offers a hint of how Google might hurry that process along. It introduces a cookies-without-same-site-must-be-secure flag that users can set so that Chrome assumes all cookies without a SameSite value are set to SameSite=Lax.

If Google applies the approach it took to HTTPS adoption to cookies, we can expect to see that flag being set by default, and the value ramped up, in later versions.

Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/PHrzeUOV4Hs/

Symantec boss Greg Clark exits biz amid dismal financials

Greg Clark, CEO and president of Symantec, has “stepped down” suddenly and with no permanent replacement lined up, just as his predecessor did.

The beleaguered security house said Clark’s departure was “effective immediately” and it named semiconductor veteran and current Symantec director Richard Hill as interim boss.

“As we enter into a new financial year, Greg and the board agreed that now is the right time to transition leadership, and we are confident in Rick’s ability to drive the company forward while we work to identify a permanent successor.”

A man spits out his coffee

Profit-strapped Symantec pulls employee share scheme

READ MORE

Clark was the boss of Blue Coat when Symantec bought the business for $4.65bn in 2016, and he was chosen to fill the vacancy left by Mike Brown, who had also left abruptly.

The changes were made public last night as Symantec outlined financial results for Q4 of its fiscal 2019, which showed a disappointing set of sales figures though cuts in expenses helped lift profit.

On a conference call, Hill – who has worked with Symantec as an advisor since October and been a director since January – said he was told by Clark in April that “he had personal issues he needed to attend and wanted to spend more time with his ageing father”.

But the timing, as Symantec released numbers for the three months ended 29 March, was impeccable: sales dipped 1.7 per cent to $1.19bn, lower than analyst estimates of $1.21bn.

“Enterprise revenue came in slightly below the low-end of our guidance range, with consumer revenue at the high-end of our guidance range,” said Nick Noviello, Symantec’s CFO, who confirmed at the end of January he is also leaving the company.

Former Logitech beancounter Vincent Pilette is taking over the finance division at Symantec.

A drop in operating expenses – lower spending on RD and general and admin costs – played a part as operating profit came in at $107m compared to $6m a year ago. Net profit was $34m versus a loss of $59m.

For the year, revenue slipped to $4.731bn from $4.834bn and net profit was just $31m, a huge dive from the $1.138bn reported a year earlier.

It has been a challenging time for Symantec: a shareholder is suing the company, claiming senior management fraudulently massaged the profit and loss accounts; 8 per cent of the workforce were axed to counter falling enterprise sales; and it was forced to launch an internal probe into claims by an ex-staffer about accounting issues, one which the SEC is now investigating too. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/05/10/symantec_ceo_quits_amid_dismal_financials/

Got SQLite? Get patching: Another RCE hole’s just been found

Cisco Talos researchers have uncovered a SQLite use-after-free vulnerability that could allow an attacker to remotely execute code on an affected device.

“An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0,” said Talos in a blog post describing the vuln, provisionally allocated CVE-2019-5018.

An open-source project, SQLite’s maintainers describe it as “the most used database engine in the world”.

SQLite implements SQL’s Window Functions, and Talos researcher Cory Duplantis found that the way SQLite handles the functions includes reusing a deleted partition.

As he noted: “After this partition is deleted, it is then reused in exprListAppendList, causing a use after free vulnerability, resulting in a denial of service. If an attacker can control this memory after the free, there is an opportunity to corrupt more data, potentially leading to code execution.”

Talos published a walkthrough, complete with examples of code highlighting precisely what the vuln is and how it exists. The fix is easy: update to SQLite version 3.28, available on the SQLite website.

Late last year, Tencent researchers spotted an SQLite vuln that could have been abused to inject malware into vulnerable systems, as we reported at the time. That one relied on memory corruption to create the conditions for arbitrary code execution, though the key vector was ordinary users being granted the privs to execute SQL commands.

Less recently, SQLite creator Dwayne Richard Hipp talked to El Reg about the project’s unabashedly Christian code of conduct. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2019/05/10/sqlite_rce_vuln/

Bumper Crop of New Briefings Added for Black Hat USA

Among the 50+ new Briefings confirmed for this August event are a deep dive into the Apple T2 chip and a pile of lessons learned from the Equifax and Home Depot breaches.

This summer Black Hat USA is coming to Las Vegas with a bumper crop of practical Trainings, Briefings, and other unique opportunities to get ahead of today’s most pressing cybersecurity threats.

To give you a taste of what’s in store, let’s highlight some of the most exciting new Briefings that have been lined up for this year’s event.

Trust and Transformation: The Post Breach Journey is a rare chance to learn all about what happened inside one of the biggest security breaches in modern memory, from someone who was there. Speaker Jamil Farshchi helped rebuild (among others) the cybersecurity systems of both The Home Depot and Equifax after their devastating data breaches in 2014 and 2017, and at Black Hat USA he’ll share vital lessons learned about issues like workplace culture, controls and compliance.

Inside The Apple T2 offers you a deep dive into the inner workings of Apple’s T2 security chip, going way beyond the limited technical details the company has made public up to now. In addition, the speakers will share their methodology along with the tools they developed and released in order to help others better understand (and research) the T2 system.

In Information Security in the Public Interest cybersecurity luminary Bruce Schneier will show you why computer security is now, fundamentally, a public policy issue. While an understanding of the technology involved is fundamental to crafting good policy, there is little involvement of technologists in policy discussions. This is not sustainable. Schneier will show you why it’s so important to have public interest technologists, and present a way forward for both you and the industry as a whole.

For more information about these great Briefings and many others check out the Black Hat USA Briefings page, which is regularly updated with new content as we get closer to the event.

Black Hat USA will return to the Mandalay Bay in Las Vegas August 3-8, 2019. For more information on what’s happening at the event and how to register, check out the Black Hat website.

Article source: https://www.darkreading.com/black-hat/bumper-crop-of-new-briefings-added-for-black-hat-usa-/d/d-id/1334667?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Hackers Still Outpace Breach Detection, Containment Efforts

Research shows time to discovery and containment of breaches slowly shrinking, but attackers don’t need a very big window to do a lot of damage.

It’s breach report season and one of the prevailing trends uncovered by security researchers is that organizations are ever-so-slowly improving the window between when a compromise occurs and when it gets detected. In spite of this slight gain, the fact solidly remains that the typical breach timeline still completely favors attackers. 

Two different reports this spring showed that organizations are shortening the time to discovery of data breaches. Most recently, the Trustwave 2019 Global Security Report released late last month found that the time between an intrusion and detection of that incident shrank almost in half. That study showed that the median time between intrusion and detection fell from 26 days in 2017 to 14 days in 2018.  

This corroborates the downward trend in this statistic identified in March by the FireEye 2019 Mandiant M-Trends Report, though that study showed a more modest reduction and a much higher time between these important breach milestones. Mandiant found that the time between intrusion and detection went down from 101 days in 2017 to 78 days in 2018. That’s marked improvement from 2011, when Mandiant put that number at 426 days.

Mandiant uses a common parlance of “dwell time” for this statistic, though other experts have their own colorful terms. But they all agree that reduction should be a big priority for cybersecurity teams.  

“We refer to the time between compromise and discovery as the ‘detection deficit,’ and a prime goal should be to have the delta between the two be as small as possible,” explained Bob Rudis, chief data scientist for Rapid7, in a blog post this week. “Note that it’s not the only goal—nor should it be the entire focus of your response plans—but it should be ‘up there’ on any top ‘x’ list you have.”

One of many industry contributors to the 2019 Verizon Data Breach Investigations Report (DBIR) released yesterday, Rudis pointed out that this year’s report shows that this detection deficit is often not even accurately measured at many organizations, which means they’re “already ceding the game’s outcome” to adversaries.

More tellingly, though, this latest DBIR shows that even with reductions like those outlined in the Trustwave and Mandiant reports, the bad guys are in another league when it comes to speed.  

“The time from the attacker’s first action in an event chain to the initial compromise of an asset is typically measured in minutes,” the 2019 DBIR report said. “Conversely, the time to discovery is more likely to be months.”

Asymmetric Battleground

different report out last month from Ponemon Institute and IBM on cyber resilience indicates that security automation is the most likely way that the security world can effectively win this asymmetric battle over dwell time.

That study showed that many gains that are being made in shortening the window between intrusion and detection are due to automation: automation improved detection and containment times by 25%. However, most organizations studied admitted they only use automation moderately, insignificantly, or not at all. Just 23% of respondents are significant users of automated tools that can reduce incident detection and response times, the study found.

Meantime, after organizations have detected and contained an event, they’re also grappling with disclosure times. This is a big issue for regulators and lawmakers these days, what with rollout of GDPR this year and rumblings of potential new laws in the US to mandate shorter disclosure times.

report released this week by Risk Based Security showed that while the time window between discovery and reporting has fallen quite a bit since 2014, that number may be on the uptick. Last year the time interval increased ever so slightly—by exactly one day—up to an average of 49.6 days. That was after a fall of more than 12 days the previous year.

The report showed that activity in first quarter of 2019 says we might be seeing a big jump in the average by the end of 2019. In the first quarter of 2019, that number increased to 54 days. 

Related Content:

 

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Article source: https://www.darkreading.com/risk/hackers-still-outpace-breach-detection-containment-efforts/d/d-id/1334669?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Symantec CEO Greg Clark Steps Down

Exec shake-up comes amid earnings drop in financial report.

Symantec this week announced an executive shakeup that included the departure of CEO Greg Clark and the naming of a new chief financial officer.

Clark, who took over the helm of Symantec in 2016 after the firm acquired Web and cloud security vendor Blue Coat Networks, where he served as CEO, for $4.65 billion. Under Clark’s tenure, Symantec acquired identity protection vendor LifeLock in late 2016 for $2.3 billion, and in 2017 formed a cybersecurity venture capital arm, Symantec Ventures, an incubator for new startups.

Richard S. Hill, Symantec director and former chairman and CEO of Novellus Systems, will serve as interim president and CEO while the company searches for a new CEO.

Meanwhile, Vincent Pilette, CFO of Logitech, was named executive vice president and CFO of Symantec. Pilette fills the slot of former Symantec CFO Nicholas Noviello, who stepped down in January.

The executive changes came as Symantec reported missed earnings for its fiscal fourth quarter. It announced earnings of $34 million on $1.19 billion in sales, a drop from $1.21 billion one year ago, according to MarketWatch.

Read more here and here

 

 

 Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/endpoint/symantec-ceo-greg-clark-steps-down/d/d-id/1334679?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

How We Collectively Can Improve Cyber Resilience

Three steps you can take, based on Department of Homeland Security priorities.

At the 2019 RSA Conference earlier this year, Chris Krebs, director of the Department of Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA), outlined several key priorities the agency is focused on for protecting US critical infrastructure. The US government is at the forefront when it comes to cybersecurity trends, so being aware of its focus can help private sector organizations improve cyber situational awareness and reduce risk.

Protecting Networks and Data from Nation-State Actors
CISA watches the usual suspects: Russia, China, Iran, and North Korea. Its key focus here is supply chain risk and minimizing the government’s attack surface by keeping what it views to be risky vendors’ equipment and applications out of US critical infrastructure networks.

In 2018, the US government banned technology from Russia-based Kaspersky Labs. With a heavy focus on China and 5G, it is now heavily focused on Huawei. Overall, the government is concerned that technology equipment from perceived risky foreign vendors could be used for malicious purposes.

Another area of focus is foreign VPN applications and, specifically, China-based applications from Dolphin, Opera, and Yandex.

Collective Cyber Defense
Krebs also discussed the importance of “collective cyber defense.” A key issue here is that we can’t fight the cyber battle alone. He indicated that multiple stakeholders have some piece of information about what’s going on — whether that’s a specific threat; tactics, techniques, and procedures; and/or vulnerabilities. It is critical that threat information is shared in a timely and practical way, and it’s hard to get the maximum effect if this information is sitting in a limited number of hands.

On a broad basis, with collective cyber defense, CISA is refining its Automated Indicator Sharing (AIS) program to include more context and specificity in order to provide more value-added threat intelligence to the private sector. 

Election security is another area in which CISA is facilitating collective defense. CISA facilitated the signing up over 1,400 local jurisdictions to the recently formed Elections Infrastructure ISAC in just a nine-month period. CISA also facilitated the deployment of intrusion detection and prevention sensors, with these now covering 90% of elections infrastructure (based on votes cast), up from 32% in 2016.

Key Takeaways
Based on CISA’s focus, there are three key things that private sector organizations can do to improve their cyber operations:

1. Increase your focus on supply chain and third-party risk. Third-party risk is a key area in security, and many large security organizations have established dedicated organizations in this area. All organizations should make moves to assess and manage this risk. This includes risks related to technology platforms that are powering your business as well as risks related to the various third-party entities with which you do business.

2. Revisit some basics regarding attack surface reduction. One easy step is to limit the use of technology from “questionable” vendors. Revisit the “who” and “what” is on your network and “whether” they should be on there. For example, if you aren’t doing business with Russia, don’t allow traffic from Russia on your network. Of course, given the global nature of business and computing, that’s not that easy for many companies, but advanced filtering capabilities like dynamic whitelisting can allow you to block traffic from a country by default while allowing access from trusted sources, such as Office 365, Amazon Web Services, content delivery networks, etc.

3. Expand your usage of threat intelligence and information sharing to benefit from collective defense.Today’s cyber threat environment requires a broader view of attacker activity than any one entity or cybersecurity vendor can provide. Expanding your use of threat intelligence can improve your cyber situational awareness and reduce risk. Easy steps here range from incorporating high-quality open source threat intelligence sources to joining DHS’s AIS program to consuming and sharing threat information with industry peers through sharing communities (information-sharing and analysis centers and organizations).

Related Content:

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

Todd Weller, Chief Strategy Officer at Bandura, works with large organizations in acting on their threat intelligence to prevent future attacks. He brings over 20 years of cybersecurity industry experience with a unique blend of operational and hands-on proficiency. He … View Full Bio

Article source: https://www.darkreading.com/risk/how-we-collectively-can-improve-cyber-resilience/a/d-id/1334606?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Microsoft SharePoint Bug Exploited in the Wild

A number of reports show CVE-2019-0604 is under active attack, Alien Labs researchers say.

Microsoft SharePoint vulnerability CVE-2019-0604 is under active attack, according to ATT Alien Labs researchers, who cite instances of exploitation from around the world.

CVE-2019-0604 is a remote code execution vulnerability that exists when SharePoint fails to verify the source markup of an application package. Exploitation requires a user to upload a specially crafted SharePoint application package to affected versions of the software. If successful, an attacker could exploit the bug and run arbitrary code in the context of the SharePoint application pool and SharePoint server farm account. Microsoft has issued a patch.

When the vulnerability was first disclosed, it was not believed to be under active attack. Now it seems a wave of attacks are exploiting this flaw and using the China Chopper web shell to gain initial access. The Saudi Arabia National Cyber Security Center reports evidence that shows several organizations have been affected by hackers using the web shell for network access. Another report, from the Canadian Cyber Security Centre, describes similar China Chopper activity.

It seems multiple attackers are now using the exploit, Alien Labs reports. Researchers found malware they say is likely an earlier version of the second-stage malware used in the Saudi attacks; the malware sample was reportedly shared by another target in China.

Read more details here.

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry’s most knowledgeable IT security experts. Check out the Interop agenda here.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/endpoint/microsoft-sharepoint-bug-exploited-in-the-wild/d/d-id/1334683?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Airbnb Superhost’s creepy spycam sniffed out by sleuthing infosec pro

An Airbnb Superhost in China who got Supercreepy with a hidden camera tucked inside a router got Superimprisoned for 20 days after a guest pulled out Superinfosec savvy and spotted the weirdly wired device.

The South China Morning Post reports that the guest, known by her online alias of Yunfei, told Beijing Youth Daily that she works in information security and, like so many righteously paranoid technophiles who stay in hotels and Airbnb listings, went about her typical routine of looking for spying apparatus when she checked in to the rental in Eastern China last week.

In Airbnb land, a Superhost is an exemplar of all that is righteous and noble in short-term hosting: we (I am one!) don’t cancel guest reservations and leave them stuck on the tarmac without a place to rest their weary bones, we answer questions quickly so as not to leave them confounded, and we get ratings that average 4.8 stars or above. In return for what one would hope is also moral rectitude and an utter lack of filming guests while they do what humans do behind closed doors, our listings get a boost in search results, and we get sweet benefits like travel credits or professional photography.

This peeping Tom of a so-called Superhost that got busted ain’t that. This host installed multiple motion detectors – one at the apartment’s entrance, and two in the two bedrooms. Weird, given that his listing, in Qingdao in Shandong province, wasn’t exactly a showcase for smart-home technology, Yunfei said:

[The motion sensor monitors were] … odd, since the flat had not been renovated for smart-home automation.

Given that she works in internet and information security, she said she’s in the habit of always checking her hotel rooms. First, she turned the sensors to face the wall and covered them with stickers. Next, she checked the smoke detectors and the TV, into which tiny spy cameras are often tucked. She also cut the power to the TV.

Then, she had a look at that router, which faced a bed. Yunfei said she noticed a light that didn’t look right, and she suspected it might be a hidden webcam.

I checked it carefully and found the line arrangement was different from the usual ones.

Sure enough, the router looked different from a photo of the product. When she took it apart, she found a digital memory card inside.

Upon finding the memory card, Yunfei immediately called the police. They came and grabbed the equipment. She had booked the place for three nights, at a cost of 1,700 yuan (USD $250), but she left and didn’t return. She hadn’t met her host, communicating solely online with him about check-in and a Wi-Fi password.

A spokesman for Airbnb told Beijing Youth Daily that they sincerely apologized to the woman, refunded her money, and yanked the host’s listing. Police later confirmed that they had arrested the host and given him a 20-day jail term.

Nothing like an infosec bod to ruin your fun filmy fantasy

So many hotel rooms and Airbnb flats, so many creeps with webcams hidden in light sockets and coat hooks and who knows where else, so much fun when somebody with an Nmap network scanner checks in!

That’s what happened in Ireland, where New Zealand infosec consultant Andrew Barker checked in to an Airbnb with his family. Barker, who routinely runs scans of networks when they check into lodgings and sign on to the Wi-Fi networks, hit the jackpot when he found a camera camouflaged to look like a smoke alarm.

His wife, Nealie Barker, wrote up their experiences in a Facebook post last month. She said at the time that it took 33 days and 10 more unsuspecting guests staying in the property (she knows because at least some of those guests contacted her) before Airbnb told her that it had removed the listing and the host.

In fact, Airbnb didn’t take action to permanently ban the host until after Nealie posted about the incident and local New Zealand news stations reported about her family’s experience.

Andrew Barker went on to write this very helpful blog post about increasing your chances of finding a hidden camera.

He explains how to thoroughly vet an Airbnb listing to see if it mentions cameras anywhere. There’s no specific field for disclosing it, he noted, so you have to comb through the listing to see if a camera is mentioned anywhere. Alternatively, if a camera shows up in any of the listing’s photos, then Airbnb considers that ample notification. If a listing makes no mention of a cam, nor includes any photo of one, then it hasn’t been disclosed, and you can get a host in hot water if you find one on the premises.

Network scanners don’t always uncover these webcams. As Barker notes, if a camera is hidden well and isn’t on the same Wi-Fi that a host has granted access to—i.e. if it’s recording to an internal memory card—or is on a network that you don’t have access to, it may be very difficult to identify.

There are other ways to spot a hidden webcam, which we’ve covered in the past. But however you find it, once you find here, here’s what to do:

What to do if you detect an undisclosed camera

Yes, this is yet another cut and paste of the same advice we give every time somebody finds one of these creepster’s spycams. But this is a new and improved version: this time, after considering a good amount of reader input, we decided that you all are correct: putting your clothes on should indeed be a priority!

  1. Get your clothes on.
  2. Take photos of the device for evidence.
  3. Take photos of your accommodation so you can prove that you haven’t trashed the place: some hosts have reportedly made such false accusations.
  4. Get out of there.
  5. Report it to police. You want to stop that stream before other people get swept up in it.
  6. If you’re in an Airbnb rental, report it to Airbnb, along with your evidence, before it happens to another victim.

Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/nGQUTcPenUk/