BRM’s Post

C2 is your trusted partner in operational resilience. ✨ But don't just take our word for it! Check out what our customers think of our services. #CustomerReview #CustomerFeedback

"Positive Preliminary Economic Assessment (“PEA”) results for the Gramalote Project; feasibility work has commenced: On June 18, 2024, the Company released the results of a positive PEA on its 100% owned Gramalote Project located in the Department of Antioquia, Colombia. Highlights of the PEA include a significant production profile with average annual gold production of 185,000 ounces over a 12.5 year project life and strong project economics with an after-tax net present value discounted at 5% (“NPV5%”) of $778 million and an after-tax internal rate of return (“IRR”) of 20.6%. B2Gold has commenced feasibility work with the goal of completing a feasibility study by mid-2025."

C2 is your trusted partner in operational resilience. ✨ But don't just take our word for it! Check out what our customers think of our services. #CustomerReview #CustomerFeedback

The timeline for Swift MT decommissioning is tighter than I realized. SimCorp's article is a wake-up call for firms delaying the migration to the ISO20022 format. How's your organization preparing? #FinancialOperations #RegulatoryCompliance #ISO20022 #SwiftMX #SimCorp

Mastering XPM 4.0: Cultivating Personal Identity, Integrity, and Goal Setting. Elevating Your Fundamentals. #nxtwave #ccbp #nxtwaveintensive

The timeline for Swift MT decommissioning is coming very fast. SimCorp's article is a wake-up call for firms delaying the migration to the ISO20022 format. How's your organization preparing? #FinancialOperations #RegulatoryCompliance #ISO20022 #SwiftMX #SimCorp

SBOMs, EPSS, CISA KEV, Reachability Analysis, CI/CD Integration, Ticketing Integration, Dependency scans, Container scans, Trend reports, Remediation recommendations, and that's just the basics. Let's talk. Here's my availability. https://lnkd.in/e8i4GiRe #applicationsecurity

Large vendors: ✅ Have their trust center in check and documentation ready. Small vendors: 🚨 Little documentation, every assessment request is a mini (or major) fire drill. Medium vendors: 🌗 Little bit of both. #thirdpartyrisk #tprm

After six months, only one IBV vendor had properly fixed the #LogoFAIL issue at the date of the disclosure, Phoenix Technologies.  However, the biggest challenge isn't fixing the reference code, it's delivering those fixes to all of the downstream vendors. Flip through the full report below to learn more.

Interesting discussion here. Who finds and releases CVE vulnerabilities when there is a fix? The vendor right? And when the vendor, or most likely the vendors customer encounters a breach due to a vulnerability we see a zero day CVE. But are vendors doing all they can to identify , notify and fix proactively? We’ve seen recently with vendors like Ivanti that’s not the case… old vulnerable code and library dependencies in outdated components were left unchecked for years. Time for a change perhaps 🤔