Showing 3434 Documents for "securities"
Filter by
Sort by
- MAS
- Media Releases
Last revised date:
- Mr Scott Charney Vice President, Security Policy, Microsoft Corporation 2. Professor Kang Meng-Chow Head, Security Assurance (Asia Pacific, Japan and China Region), Amazon Web Services 3. Mr David Koh Chief Executive, Cyber Security Agency of Singapore 4.
- Ms Cheri McGuire Group Chief Information Security Officer, Standard Chartered Bank 5. Mr John Nai Chief Information Security Officer, PayPal 6. Mr Erik Ploegmakers Managing Director, Fox-IT 7.
- Singapore, 30 September 2019… The Monetary Authority of Singapore (MAS)’s Cyber Security Advisory Panel (CSAP) For more information on MAS’ CSAP, please refer to: https://www.mas.gov.sg/who-we-are/MAS-Advisory-Panels-and-Committees/Cyber-Security-Advisory-Panel meeting convened today to discuss the latest
- MAS
- Consultations
Last revised date:
- Representatives who want to deal in NEIPs that fall within the definition of securities and futures contracts will generally have to pass the new CMFAS module for securities and futures contracts.
- and individual European jurisdictions governing Undertakings for Collective Investment in Transferable Securities (UCITS).
- Broker-dealers are required to perform similar due diligence in approving a customers account for security futures trading.
- MAS
- Media Releases
Last revised date:
- fund management activities respectively under the SFA, and would ordinarily require the providers of such services to hold a capital markets services licence under the SFA, unless otherwise exempted.
- To make it easier for entities offering digital advisory services to operate in Singapore, the guidelines also set out refinements in the licensing and business conduct requirements under the Securities and Futures Act (SFA) and Financial Advisers Act (FAA) as follows: a) Digital advisers that seek to
- Providers of digital advisory services are required to be licensed under the SFA and/or the FAA. The type of licence required depends on the entity’s scope of activities and business model.
- MAS
- Media Releases
Last revised date:
- (ii) Under section 232 of the SFA, MAS may enter into an agreement with any person for that person to pay, with or without admission of liability, a civil penalty for contravening any provision of Part XII of the SFA.
- Singapore, 20 May 2014… The Monetary Authority of Singapore (MAS) has taken civil penalty enforcement action against Mr Koh Huat Heng for insider trading under Section 219(2)(a) of the Securities & Futures Act (SFA). 2 Mr Koh was a relationship manager and a Team Head in the Affluent Banking Unit of
- , from subscribing for, purchasing, selling, or entering into an agreement to subscribe for, purchase or sell those securities of that corporation.
- MAS
- Media Releases
Last revised date:
- with our Cyber Security Advisory Panel.
- The panel recommended that FIs further fortify the security of digital banking services.
- The panel highlighted that DLT related security solutions are still nascent, and not well understood by many solution implementors.
- MAS
- Consultations
Last revised date:
- on foreign securities exchanges recognised by the Authority.
- or units in a collective investment scheme, the value of the specified securities or units of the collective investment scheme (as the case may be) at a specified future time; and (b) where the underlying thing of the warrant is any securities index, the value of the securities index at a specified
- The definition of excluded warrants in the Notice will cover: existing daily leverage certificates; and (i) (ii) structured warrants based on securities, units in a business trust, units in a collective investment scheme, or indices comprising such securities and/or units, which are listed
- MAS
- Speeches
Last revised date:
- Only facilities designated by MAS will be regulated under the SFA.
- The amendments to the SFA passed by Parliament recently will allow MAS to do this. 35 The MAS consultation proposals relating to exchanges and trading platforms are aimed at better focusing the scope of the SFA.
- MAS will soon be seeking feedback on the second phase of amendments to the Securities and Futures Act in 2004.
- PDPC
- Commission's Decisions
Last revised date:
- The security code fix was meant to be deployed into the enterprise environment (which was a test environment) for further testing.
- , including identifying areas of high risk that require higher level of approval and adequate supervision.5 In the present case, the deployment of the security code fix into the ActiveSG App could potentially expose the Disclosed Data and the Additional Disclosed Data to security risks
- The Organisation also developed, deployed and operated the SSCMMS (including the ActiveSG App). 4 On 1 March 2019, the Organisations engineer developed a security code fix for the ActiveSG App.
- PDPC
- Commission's Decisions
Last revised date:
- Prudential had reasonable policies in place which dealt with proper and secure disposal of clients policy documents.
- In this case, a reasonable security arrangement meant proper and secure disposal of the Prudential folders, which would prevent any of the risks mentioned. 15 The PDPCs Guide to Disposal of Personal Data on Physical Medium (PDPCs Guide to Disposal) sets out some useful principles
- Section 24 requires an organisation to make reasonable security arrangements to prevent unauthorised access, collection, use, disclosure, copying, modification, disposal or similar risks.
- PDPC
- Commission's Decisions
Last revised date:
- This explanation is not accepted. 12 As emphasized in previous decisions and the Commissions Guide to Securing Personal Data in Electronic Medium (revised 20 January 2017) at [16.3] and [16.4], regular security testing and patching of IT systems are important security measures that organisations
- In assessing the standard of reasonable security arrangements required, I considered the fact that Employee Data included NRIC numbers and personal data of a financial nature (i.e.
- [2019] SGPDPC 47 11 The Organisation admitted that it had not carried out any security scans, penetration testing or patching of the VM Server for at least 12 months preceding the Incident.