- The Office of the Australian Information Commissioner (OAIC) welcomes the opportunity to provide comments in relation to the draft Telecommunications (Mobile Number Pre-Porting Additional Identity Verification) Industry Standard 2020 (draft standard).
- The OAIC notes the Telecommunications (Industry Standard for Mobile Number Pre-Porting Additional Identity Verification) Direction made by the Minister for Communications, Cyber Safety and the Arts in October 2019 (the Determination). The Determination directs the Australian Communications and Media Authority (ACMA) to make an industry standard that requires gaining mobile carriage service providers (CSPs) to implement customer identity verification processes before accepting a port of a mobile service number, in the Government’s efforts to combat mobile porting fraud and to protect the personal information of Australians.
- Under section 134 of the Telecommunications Act 1997 (Telecommunications Act), the ACMA must consult with the OAIC before determining an industry standard on matters dealt with by the Australian Privacy Principles (APPs) or other provisions of the Privacy Act 1988 (Privacy Act) relating to those principles.
- The OAIC handles complaints about acts and practices that may be an interference with privacy under the Privacy Act, a principles-based framework for privacy protection in Australia. In undertaking this function, the OAIC has received complaints involving CSPs and unauthorised porting that has resulted in alleged identity theft and unauthorised access to personal information.
- In assessing these matters the OAIC considers, among other matters, ‘reasonable steps’ the CSP has taken under APP 10 (quality of personal information) and APP 11 (security of personal information) to verify the identity of an individual before porting their number.
- The OAIC welcomes measures to strengthen pre-porting identity verification requirements, which aim to enhance privacy protections for individuals and their personal information.
Requirements under the Privacy Act
- Under the Privacy Act, pre-porting verification processes will be covered most relevantly by APPs 10 and 11, contained in Schedule 1 of the Privacy Act. APP 1, the foundational governance principle, also requires APP entities to take reasonable steps to implement practices, procedures and systems that will ensure compliance with the APPs and deal with enquiries and complaints.
- Under APP 10, CSPs that are ‘organisations’ under the Privacy Act must take such steps ‘as are reasonable in the circumstances’ to ensure personal information that the entity uses or discloses, having regard to the purpose of the use or disclosure, is accurate, up-to-date and complete.
- An example of taking ‘reasonable steps’ under APP 10 to ensure quality of personal information may include implementing internal practices, procedures and systems to audit, monitor, identify and correct poor quality personal information, including in time-critical situations, such as a number porting request.
- Under APP 11, CSPs must take such steps ‘as are reasonable in the circumstances’ to protect personal information:
- from misuse, interference and loss; and
- from unauthorised access, modification or disclosure.
- An example of taking ‘reasonable steps’ under APP 11 to ensure security of personal information may include taking steps and implementing strategies relating, but not limited to:
- governance, culture and training;
- internal practices, procedures and systems;
- ICT security;
- third party providers, including cloud computing;
- data breaches;
- physical security;
- destruction and de-identification; or
- The OAIC notes pre-porting verification requirements in the draft standard supplement the Industry Code – Mobile Number Portability (C570:2009) (Code) and Customer Authorisation Industry Guideline (G651:2017) (Guideline).
- The OAIC notes section 116A of the Telecommunications Act provides that neither an industry code nor an industry standard derogates from a requirement made by, or under the Privacy Act. The OAIC considers that entities should be made aware that the requirements of the Privacy Act continue to apply in addition to the standard. CSPs may be compliant with telecommunications industry codes and guidelines, but still be in breach of certain APPs, such as where the OAIC considers all ‘reasonable steps’ have not been taken in the particular circumstances.
At the end of section 8 of the draft standard, or another section as appropriate, we recommend inserting words to the following effect:
Note: Section 116A of the Telecommunications Act 1997 provides that neither an industry code nor an industry standard derogates from a requirement made by or under the Privacy Act 1988.
Requirements for GCSPs during a Customer Authorisation (CA)
- Section 8 of the draft standard sets out new minimum requirements for authorising porting requests by adding the requirement for a gaining carriage service provider (GCSP) to use at least one ‘additional identity verification process’ prior to accepting the port of a mobile service number.
- The OAIC supports the outcomes-based approach taken by the ACMA to consider variance between CSPs while maintaining high standards of safeguards. Paragraph 8(2)(d) of the draft standard appears to allow for flexibility in implementation of the additional identity verification requirements to cater for differences in CSPs’ size, scale of operation and interaction with customers.
Requirements for LCSPs during a CA
- Currently, the draft standard does not impose any requirements on the Losing Carriage Service Provider (LCSP) to conduct identification processes during a CA, despite the fact it is the party already familiar with the customer and holding their personal information. The LCSP has obligations under APP 1 (open and transparent management of information), APP 6 (use or disclosure of personal information) and APP 11 (security of personal information) to ensure that the personal information of customers is not improperly disclosed to GCSPs. There is a risk of improper disclosure in the event that an unauthorised porting request is made. The OAIC considers that the CA process would be improved by mandating additional verification requirements across both the LCSP and GCSP.
The draft standard does not impose any obligations on the LCSP. The ACMA should consider whether the privacy protections in the draft standard could be strengthened by requiring that the LCSP also has obligations in relation to additional identity verification requirements.
CSPs that are ‘small businesses’ under the Privacy Act
- Some small businesses are exempt from the Privacy Act. A CSP that is defined as a ‘small business’ for the purposes of the Privacy Act does not have to comply with that Act. There is therefore a parallel risk that customers’ personal information that is collected, held, used and disclosed in connection with this standard would not be protected under that Act, and not covered under APPs 10 and 11.
- In order to protect customers’ personal information, we recommend any CSPs who are not subject to the Privacy Act be required to opt-in to coverage under section 6EA of the Privacy Act. This will ensure that customers are afforded equal and consistent privacy protections irrespective of the size of CSP.
We recommend that the ACMA includes a requirement in the draft standard that CSPs that are ‘small businesses’ be required to opt in to the Privacy Act under section 6EA of that Act.
15. For further information please contact Kellie Fonseca, Director, Regulation & Strategy, via [contact details removed] if you would like to discuss this matter further.
 APPs 10.1 and 10.2.
 APPs 11.1 and 11.2.
 Section 4 of the draft standard.
 Section 116A of the Telecommunications Act 1997.
 ACMA Consultation Paper – Proposal to make the Telecommunications Mobile Number Pre-Porting Additional Identity Verification Industry Standard 2020.
 Clauses 4 and 5 of the G651:2017 (Customer Authorisation Industry Standard).
 Sections 6C and 6D of the Privacy Act.
Was this page helpful?
If you would like to provide more feedback, please email us at email@example.com