28 controls
39 frameworks share controls with it
Samoa
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
SAM-1 | Customer Information Confidentiality (Section 48) | 39 |
SAM-2 | Consent Requirements | 0 |
SAM-5 | Government Access to Information (Section 51) | 0 |
SAM-6 | Legal Authorization Requirements | 39 |
SAMOATEL-1 | Scope and Lawful Processing | 0 |
SAMOATEL-2 | Consent and Rights | 0 |
SAMOATEL-3 | Security and Cross-Border | 0 |
SAMOATEL-4 | Enforcement | 0 |
STA-1 | Confidentiality of Communications | 0 |
STA-10 | Security Safeguards over Networks and Systems | 0 |
STA-11 | Incident Notification | 0 |
STA-12 | Customer Access to Their Own Information | 0 |
STA-13 | Encryption of Sensitive Customer Data | 0 |
STA-14 | Logging of Access to Customer Data | 0 |
STA-15 | Regulator Cooperation | 0 |
STA-16 | Privacy by Design in New Services | 0 |
STA-17 | Cross Border Transfer Controls | 0 |
STA-18 | Complaint Handling | 0 |
STA-19 | Recording of Calls and Communications | 0 |
STA-2 | Lawful Interception and Disclosure Controls | 0 |
STA-20 | Number and Identifier Protection | 0 |
STA-3 | Customer Personal Data Handling | 0 |
STA-4 | Access Control over Subscriber Records | 0 |
STA-5 | Traffic and Metadata Protection | 0 |
STA-6 | Employee Confidentiality Undertakings | 0 |
STA-7 | Third Party Provider Obligations | 0 |
STA-8 | Data Retention Limits | 0 |
STA-9 | Marketing Use of Customer Data | 0 |
Tell me when Samoa Telecommunications Act (2005) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Risk assessment process
- Fraud-risk consideration
- Risk responses
- Annual risk assessment report
- Threat modelling output
- Risk register with treatment decisions
- Customer information confidentiality policy aligned to Section 48
- Consent capture records and templates
- Access control records for customer information
- Staff training records on confidentiality obligations
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for Samoa Telecommunications Act (2005), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition