Purpose
Identify ways to reduce login friction while preserving security controls.
Explore details →
A review of authentication controls and potential improvements.
Identify ways to reduce login friction while preserving security controls.
Explore details →Public-source review and selected screens from the October 21 UAT recording.
Explore details →Validate scope, evidence and control ownership after authorized access.
Explore details →This review identifies opportunities to simplify the login journey while retaining required safeguards. The current production configuration and internal requirements have not been reviewed.
Barings LLC is an SEC-registered adviser; portal and data scope require confirmation.
Confirm data scope, safeguards, incident response and service-provider oversight.
Explore details →Review policies, annual effectiveness testing and corrective actions under Rule 206(4)-7.
Explore details →Review access, account management, cyber recovery and third-party risk. Staff priorities are not new rules.
Explore details →Confirm whether the relevant entity and data fall within scope. Covered institutions must maintain safeguards, incident-response procedures and service-provider oversight. Institutional use alone does not settle data coverage.
Map the operating entity and service, not just the institutional client’s location.
For in-scope entities, review risk-based internal ICT audit and follow-up of critical findings.
Explore details →Confirm the firm category and whether independent internal audit is appropriate and proportionate.
Explore details →Review technology-risk guidance and map applicable binding notices. Do not assume bank rules apply.
Explore details →For relevant in-scope entities other than microenterprises, the ICT risk-management framework is subject to regular internal audit with risk-based frequency and formal follow-up of critical findings. An EU visitor alone does not establish scope.
Different reviews answer different questions. Report scope and client commitments matter.
A financial audit is not proof of login controls. SOC 1 addresses financial reporting controls; confirm custody-rule scope.
Explore details →SOC 2 and ISO 27001 address different forms of assurance. Check the scope, controls and exceptions.
Explore details →Review contracts, security commitments and client audit rights using the actual wording.
Explore details →Financial audits and SOC 1 focus on financial reporting. Some IT controls can be in scope, but these reviews do not by themselves demonstrate comprehensive login protection. Custody-rule applicability depends on the actual arrangements.
Proposed direction: reduce routine CAPTCHA friction while retaining effective protection against automated abuse.
Obtain an approved revision or exception; document the replacement and residual risk.
Explore details →Review the original remediation and wording, then obtain the required approvals.
Explore details →Test retained or replacement controls against the objective and record the approval.
Explore details →Evaluate the replacement, seek the appropriate approved policy revision or exception, and document residual risk. Do not change a policy solely to justify an unsupported removal.
Validate the actual platform, policies and supported flows before choosing a configuration.
Consider risk-triggered Auth Challenge, brute-force blocking, suspicious-IP throttling and monitored attack events.
Explore details →Consider enforced Okta Challenge, ThreatInsight enforcement and system-log monitoring. Confirm entitlement and supported flows.
Explore details →Consider guided authenticator-app enrollment and retain approved recovery. TOTP is not phishing-resistant; preserve any stronger assurance requirement.
Explore details →If Auth0 enforces this flow, assess risk-triggered Auth Challenge, brute-force blocking and suspicious-IP throttling, with monitored events. Confirm supported flows, entitlement, configuration and false-positive impact.