TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

JPMC: An open letter to third-party suppliers

36 pointsby kossae26 days ago

2 comments

EdwardKrayer25 days ago
Ironic that JPMorgan Chase demands suppliers improve security while neglecting basic practices, like crediting vulnerability researchers [1]. With 18% YoY profit growth in 2024 [2], they could easily allocate additional resources to drive meaningful industry-wide change that would benefit all of us.<p>Maybe the real issue is they choose to bring in lower quality suppliers that they deemed to be &quot;good enough&quot;, instead of hiring quality, and building robust internal process to make sure the type of feedback is brought to the suppliers directly - with examples, and well thought out suggestions instead of this notice posted on the office fridge.<p>To me, this looks like a lack of will for financial commitment rather than an industry-wide plague that&#x27;s impervious to the ultimate resource to fix nearly every problem we face - willpower and an increased budget.<p>[1]: <a href="https:&#x2F;&#x2F;www.linkedin.com&#x2F;posts&#x2F;shubhankargaur_jpmorganchase-vapt-bugbounty-activity-7118668328981700610-KrHA" rel="nofollow">https:&#x2F;&#x2F;www.linkedin.com&#x2F;posts&#x2F;shubhankargaur_jpmorganchase-...</a><p>[2]: <a href="https:&#x2F;&#x2F;www.reuters.com&#x2F;business&#x2F;finance&#x2F;jpmorgan-profit-jumps-dealmakers-traders-ride-market-rebound-2025-01-15&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reuters.com&#x2F;business&#x2F;finance&#x2F;jpmorgan-profit-jum...</a>
pledess18 days ago
The letter mentions OAuth but doesn&#x27;t mention the ongoing work to address the <a href="https:&#x2F;&#x2F;eprint.iacr.org&#x2F;2025&#x2F;629" rel="nofollow">https:&#x2F;&#x2F;eprint.iacr.org&#x2F;2025&#x2F;629</a> findings, CVE-2025-27371.