
GoSecure Announces Titan Platform Spring Update
Update enhances MDR service to detect ransomware and malware faster La Jolla, CA. — GoSecure, a leading provider of Managed Detection and Response...
GoSecure Titan® Managed Extended Detection & Response (MXDR)
GoSecure Titan® Managed Extended Detection & Response (MXDR) Foundation
GoSecure Titan® Vulnerability Management as a Service (VMaaS)
GoSecure Titan® Managed Security Information & Event Monitoring (Managed SIEM)
GoSecure Titan® Managed Perimeter Defense (MPD)
GoSecure Titan® Inbox Detection and Response (IDR)
GoSecure Titan® Secure Email Gateway (SEG)
GoSecure Titan® Threat Modeler
GoSecure Titan® Identity
GoSecure Professional Security Services
Incident Response Services
Security Maturity Assessment
Privacy Services
PCI DSS Services
Penetration Testing Services
Security Operations
GoSecure MXDR for Microsoft
Comprehensive visibility and response within your Microsoft security environment
USE CASES
Risk-Based Security Measures
Safeguard sensitive information
Make informed decisions
Fulfill regulatory obligations
A valuable risk management strategy
Combat ransomware with innovative security
Halt zero-day exploits with advanced protection
Get ahead and win the race with the GoSecure Titan® Platform
24/7 MXDR FOUNDATION
GoSecure Titan® Endpoint Detection and Response (EDR)
GoSecure Titan® Next Generation Antivirus (NGAV)
GoSecure Titan® Security Information & Event Monitoring (SIEM)
GoSecure Titan® Inbox Detection and Reponse (IDR)
GoSecure Titan® Intelligence
ABOUT GOSECURE
GoSecure is a recognized cybersecurity leader and innovator, pioneering the integration of endpoint, network, and email threat detection into a single Managed Extended Detection and Response (MXDR) service. For over 20 years, GoSecure has been helping customers better understand their security gaps and improve their organizational risk and security maturity through MXDR and Professional Services solutions delivered by one of the most trusted and skilled teams in the industry.
LATEST PRESS RELEASE
Update enhances MDR service to detect ransomware and malware faster La Jolla, CA. — GoSecure, a leading provider of Managed Detection and Response...
GOSECURE BLOG
For the sixth year, GoSecure is encouraging...
Author: Andréanne Bergeron To explore how a...
Rampant inflation is driving an increase in...
RESOURCES
SECURITY ADVISORIES
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
We have previously talked about LinkedIn having an endpoint for Outlook profile cards. This endpoint is receiving email addresses as input and returns the complete profile information (name, company, location, etc.). These sorts of APIs can be abused for OSINT.
To reproduce the set-by-step tutorial your will need an Outlook account (@hotmail.com, @live.com or outlook.com email), the latest version of ZAP and our WebSocket plugin.
Aurelia is one of many JavaScript frameworks available for front-end developers. Although nowadays, it is not as popular as Angular or React, its user base is not negligible: It has more than 11,000 stars and over a hundred contributors on its GitHub page. However, if you are one of its users, you need to be aware of its insecure default HTML sanitizer: relying solely on it to filter malicious input may leave you vulnerable to Cross Site Scripting (XSS) attacks.
When we were looking at the interactions between the Outlook and the LinkedIn APIs, we encountered WebSocket communications that used some additional encoding. The encoding was nothing too complex, but it was uncommon. It turned out to be LZip compression. However, the inability to read the content of the requests with Burp, ZAP or Web developer consoles in real-time made it difficult to analyze the API.
In this blog post, we will look at the privacy issues with some of LinkedIn’s external APIs. We will demonstrate how it is possible, with an email address, to find its associated LinkedIn profile. It is also possible from a LinkedIn profile to do the reverse path and find a person’s email address. To execute this deanonymization attack, documented features, like LinkedIn’s integration with Outlook and YahooMail, are used.
If you are testing the security of WordPress websites, you will likely have to look at the REST endpoints. By default, users can be listed with the route “/wp-json/wp/v2/users”. On the latest WordPress version, out of the box, you will get the username and the hashed email. Experienced WordPress administrators and users are aware of the potential disclosure. Therefore, we can see various tutorials online on how to hide this information. The recommended ways are either to disable the REST API completely, install a security plugin which disables the specific route or block specific request paths.