securelayer7.github.io/index.xml at master · securelayer7/securelayer7.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Securelayer7</title>
    <link>https://securelayer7.github.io/</link>
    <description>Recent content on Securelayer7</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright © 2019 SecureLayer7, LLC. All rights reserved.</copyright>
    <lastBuildDate>Wed, 17 Jul 2019 00:00:00 +0000</lastBuildDate>

	<atom:link href="https://securelayer7.github.io/index.xml" rel="self" type="application/rss+xml" />


    <item>
      <title>Reading data from EEPROM without desoldering</title>
      <link>https://securelayer7.github.io/posts/reading-firmware-from-eeprom-easyway/</link>
      <pubDate>Wed, 17 Jul 2019 00:00:00 +0000</pubDate>

      <guid>https://securelayer7.github.io/posts/reading-firmware-from-eeprom-easyway/</guid>
      <description>Introduction In IoT/Hardware security it is common practice of dumping firmware/bootloader data inorder to perform reverse engineering for closed source system applications.
Well known easiest way is to download .bin/.zip (packed firmware) files from device manufacturer&amp;rsquo;s website which they provide to end users for firmware upgrade operations. And later us hackers/security researchers throw these files to reverse engineering softwares such as binwalk to check it&amp;rsquo;s contents and extract the needed stuff.</description>
    </item>

    <item>
      <title>XSS Auditor no more part of Google Chrome</title>
      <link>https://securelayer7.github.io/posts/xss-auditor-no-more-part-of-google-chrome/</link>
      <pubDate>Tue, 16 Jul 2019 00:00:00 +0000</pubDate>

      <guid>https://securelayer7.github.io/posts/xss-auditor-no-more-part-of-google-chrome/</guid>
      <description>Yes, you heard correct Google Chromium devs announced the news about XSS auditor. The XSS auditor time and again bypassed by the client security researcher to execute the malicious javascript, and this may be the primary reason to be deprecated and removed from the Google Chrome browser.
The anti-cross site scripting engine (XSS auditor) is not covering all XSS type such as DOM-based XSS, mXSS, and persistent XSS. XSS auditor mostly working on for the reflected XSS, and this is again can be bypassed by tricking the Javascript payload.</description>
    </item>

    <item>
      <title>SecureLayer7 at RISE Conference, Hong Kong 2019</title>
      <link>https://securelayer7.github.io/posts/rise-conference-2019/</link>
      <pubDate>Sun, 07 Jul 2019 00:00:00 +0000</pubDate>

      <guid>https://securelayer7.github.io/posts/rise-conference-2019/</guid>
      <description>Watch7 AuthSafe The SecureLayer7’s Watch7 AuthSafe is user and entity behavior analytics which gets integrated with applications. AuthSafe provides the account security that disallows attacker to access the account even if attacker has valid credentials.
Watch7 LogSight The SecureLayer7’s Watch7 LogSight is a threat detection platform that finds high-quality threats in the infrastructure from logs and shares the threat details to give you the quick way of eradicating attacks in infrastructure.</description>
    </item>

    <item>
      <title>Identifying UART Pins Without a Multi-Meter (PinNinja)</title>
      <link>https://securelayer7.github.io/posts/identifying-uart-pins-without-a-multi-meter/</link>
      <pubDate>Thu, 27 Jun 2019 00:00:00 +0000</pubDate>

      <guid>https://securelayer7.github.io/posts/identifying-uart-pins-without-a-multi-meter/</guid>
      <description>As someone who likes to tinker with hardware, we often find ourselves opening up a device to find UART pins which are originally meant for debugging and testing We often use these to connect to the device. But most of us hit a small snag here.
Snag No 1: More often than not the pins are not labeled.
(So you mean they put those pins there so we can test the device but didn’t tell what pin was what because they didn’t want us to test it?</description>
    </item>

    <item>
      <title>About</title>
      <link>https://securelayer7.github.io/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://securelayer7.github.io/about/</guid>
      <description>COMPANY SecureLayer7 is an international provider of integrated business information security solutions with an innovative approach to IT security.
SecureLayer7 founded in 2012 with the vision to solve the toughest cybersecurity problems faced by today’s leading organisations and provide actionable solutions. The foundation of the company motivated for protecting users from increasingly sophisticated cyber-attacks and provide quality service over the years serving the ever-changing cybersecurity environment.
SecureLayer7 is CERT-in accredited cybersecurity company and certified security consultants, we consult business of all size across the United States of America, Europe, UK, Middle-east, and East Asia in both public and private companies.</description>
    </item>

  </channel>
</rss>