@cclabsnz/sf-audit 1.11.0 → 1.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -11,6 +11,44 @@ published note and carries the signed provenance attestation and CycloneDX SBOM
11
11
 
12
12
  Merged to `main`, not yet released.
13
13
 
14
+ ## [v1.12.0](https://github.com/cclabsnz/sf-audit-plugin/releases/tag/v1.12.0) — 2026-09-07
15
+
16
+ A check that shipped in the source but never ran, now registered, plus tests for three more.
17
+
18
+ ### Added
19
+
20
+ - **`soap-login-api-auth`** — flags accounts that authenticate with SOAP API `login()` but do not
21
+ hold the "Use Any API Auth" permission that Winter '27 requires, and separately flags holders
22
+ that no longer need it.
23
+
24
+ The check class has been present and compiling since Winter '27 planning and **had never run**:
25
+ its registry, compliance, `CheckMeta` and test wiring were deferred behind another unfinished
26
+ check and then forgotten. An unregistered check is invisible to the whole suite, so nothing
27
+ failed. It runs now.
28
+
29
+ Worth stating because published coverage of this change routinely gets it wrong: "Use Any API
30
+ Auth" is **not** the same permission as "Use Any API Client", which the separate
31
+ `api-client-permission` check covers. Granting the wrong one leaves the breakage in place while
32
+ feeling remediated. The compliance mapping deliberately does not reuse the Use Any API Client
33
+ control, for the same reason.
34
+
35
+ Both halves matter. The missing-permission half is an availability finding: the failure lands at
36
+ authentication, server to server, with no error anywhere in the Salesforce UI. The
37
+ already-granted half is a security finding, because granting broadly at profile level is the
38
+ common response to this change and converts a breakage problem into a standing-privilege one.
39
+
40
+ ### Changed
41
+
42
+ - Check count is now **92**.
43
+
44
+ ### Internal
45
+
46
+ - Unit tests added for `connected-apps`, `connected-app-inactivity` and `api-client-permission`.
47
+ Untested checks drop from 36 to 33 of 92. The `connected-apps` tests pin the
48
+ `connectedAppNames` cache write that two other checks read, and the `api-client-permission`
49
+ tests assert on the query text so a copy-paste between the two easily-confused API permissions
50
+ fails a test.
51
+
14
52
  ## [v1.11.0](https://github.com/cclabsnz/sf-audit-plugin/releases/tag/v1.11.0) — 2026-09-07
15
53
 
16
54
  One new check, closing a blind spot that the SaaS token-theft campaigns of the last year
package/README.md CHANGED
@@ -15,7 +15,7 @@
15
15
 
16
16
  A Salesforce CLI (`sf`) plugin that runs a complete, **read-only** security audit against any Salesforce org, risk-scores it with an A–F grade, and turns the result into a report your security team (or your client's) can act on.
17
17
 
18
- - **91 read-only checks** across identity, access, data, code, integrations, monitoring, and Agentforce / GenAI
18
+ - **92 read-only checks** across identity, access, data, code, integrations, monitoring, and Agentforce / GenAI
19
19
  - **Attack-chain correlation:** links individual findings into named, multi-step attack scenarios — eleven modelled chains, plus an emergent pass for combinations nobody has named yet (see [Attack chains](#attack-chains))
20
20
  - **Compliance mapping:** every finding mapped to **source-verified** controls across 10 frameworks (OWASP, OWASP LLM Top 10, SOC 2, ISO/IEC 27001:2022, Security Benchmark for Salesforce, NZ Privacy Act, HISO 10029, NZISM, HIPAA Security Rule, GDPR)
21
21
  - **Outputs:** a technical `html` / `md` / `json` report, or a branded, client-ready **executive report** (print-to-PDF) with priorities, remediation roadmap, and a compliance coverage matrix
@@ -44,7 +44,7 @@ guarantees here are checkable rather than asserted — see [Trust & verification
44
44
  sf audit security --target-org <orgAlias>
45
45
  ```
46
46
 
47
- Runs all 91 checks and writes an HTML report to the current directory. `sf audit list` prints every
47
+ Runs all 92 checks and writes an HTML report to the current directory. `sf audit list` prints every
48
48
  check id.
49
49
 
50
50
  | Flag | Default | |
@@ -94,13 +94,13 @@ All twelve flags, more examples, and what the executive report contains:
94
94
 
95
95
  ## What It Checks
96
96
 
97
- **91 read-only checks** across ten domains. Every finding is risk-rated CRITICAL → INFO, mapped to
97
+ **92 read-only checks** across ten domains. Every finding is risk-rated CRITICAL → INFO, mapped to
98
98
  compliance controls, and correlated into [attack chains](#attack-chains).
99
99
 
100
100
  | Domain | Checks |
101
101
  |--------|-------:|
102
102
  | Identity & Authentication | 13 |
103
- | Users, Permissions & Privilege | 12 |
103
+ | Users, Permissions & Privilege | 13 |
104
104
  | Data Access & Sharing | 11 |
105
105
  | Guest & External-Facing Access | 12 |
106
106
  | Integrations, Connected Apps & Deployments | 11 |
@@ -26,6 +26,7 @@ import { StandardProfilesCheck } from './impl/StandardProfilesCheck.js';
26
26
  import { SsoEnforcementCheck } from './impl/SsoEnforcementCheck.js';
27
27
  import { MfaEnforcementCheck } from './impl/MfaEnforcementCheck.js';
28
28
  import { ApiClientPermissionCheck } from './impl/ApiClientPermissionCheck.js';
29
+ import { SoapLoginApiAuthCheck } from './impl/SoapLoginApiAuthCheck.js';
29
30
  import { IntegrationUsersCheck } from './impl/IntegrationUsersCheck.js';
30
31
  import { IntegrationLeastPrivilegeCheck } from './impl/IntegrationLeastPrivilegeCheck.js';
31
32
  import { ContentLinksCheck } from './impl/ContentLinksCheck.js';
@@ -128,6 +129,7 @@ export const CHECKS = [
128
129
  new SsoEnforcementCheck(), // SBS-AUTH-001/002
129
130
  new MfaEnforcementCheck(), // SBS-AUTH-004 (portal users)
130
131
  new ApiClientPermissionCheck(), // SBS-ACS-006
132
+ new SoapLoginApiAuthCheck(), // Winter '27 SOAP login() readiness; distinct from Use Any API Client above
131
133
  new IntegrationUsersCheck(), // SBS-ACS-007/008/009
132
134
  new IntegrationLeastPrivilegeCheck(), // permissions integration accounts hold and do not use
133
135
  new ContentLinksCheck(), // SBS-FILE-001/002/003
@@ -31,6 +31,7 @@ const BASE_CHECK_CONTROL_MAP = {
31
31
  'sso-enforcement': ['OWASP-A07', 'SOC2-CC6.1', 'ISO-A.8.3', 'SBS-AUTH-001', 'SBS-AUTH-002'],
32
32
  'mfa-enforcement': ['OWASP-A07', 'SOC2-CC6.1', 'ISO-A.8.3', 'SBS-AUTH-004'],
33
33
  'api-client-permission': ['OWASP-A01', 'SOC2-CC6.3', 'ISO-A.8.3', 'SBS-ACS-006'],
34
+ 'soap-login-api-auth': ['OWASP-A01', 'SOC2-CC6.1', 'ISO-A.5.18'],
34
35
  'integration-users': ['OWASP-A01', 'SOC2-CC6.1', 'ISO-A.5.18', 'SBS-ACS-007', 'SBS-ACS-008', 'SBS-ACS-009'],
35
36
  'integration-least-privilege': ['OWASP-A01', 'SOC2-CC6.3', 'ISO-A.5.18', 'SBS-ACS-008', 'SBS-ACS-009'],
36
37
  'content-links': ['OWASP-A01', 'SOC2-CC6.1', 'ISO-A.5.14', 'SBS-FILE-001', 'SBS-FILE-002', 'SBS-FILE-003'],
@@ -114,7 +115,7 @@ const BASE_CHECK_CONTROL_MAP = {
114
115
  // so the two cannot drift apart in which checks they consider part of a domain.
115
116
  const DOMAIN = {
116
117
  accessControl: ['users-and-admins', 'permissions', 'sharing-model', 'public-group-sharing', 'guest-user-access',
117
- 'field-level-security', 'standard-profiles', 'api-client-permission', 'integration-users',
118
+ 'field-level-security', 'standard-profiles', 'api-client-permission', 'soap-login-api-auth', 'integration-users',
118
119
  'integration-least-privilege',
119
120
  'escalation-perms', 'report-folder-access', 'apex-crud-fls', 'apex-rest-endpoint',
120
121
  'guest-executable-apex', 'experience-cloud-site', 'content-links', 'apex-sharing', 'flows-without-sharing',
@@ -26,6 +26,7 @@ export const CHECK_META = {
26
26
  'sso-enforcement': { effort: 'project', impact: 'Without enforced SSO, username/password logins bypass your identity provider’s MFA and conditional access.' },
27
27
  'mfa-enforcement': { effort: 'quick', impact: 'Portal/external users without MFA let a stolen password reach customer or partner data directly.' },
28
28
  'api-client-permission': { effort: 'quick', impact: '“Use Any API Client” bypasses API Access Control, letting a user reach the org from any tool.' },
29
+ 'soap-login-api-auth': { effort: 'quick', impact: 'SOAP login() callers without Use Any API Auth stop authenticating in Winter \'27, server to server, with no UI error.' },
29
30
  'integration-users': { effort: 'moderate', impact: 'Over-privileged service accounts are prime targets: one stolen key grants broad, unattended access.' },
30
31
  'integration-least-privilege': { effort: 'moderate', impact: 'An integration account keeps whatever it was granted at go-live: long-lived credentials, no interactive user to notice misuse, and frequently outside MFA and IP restrictions. Every permission it is not using is standing privilege waiting on a leaked key.' },
31
32
  'content-links': { effort: 'quick', impact: 'Public file links without expiry or password leak documents to anyone who finds the URL.' },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cclabsnz/sf-audit",
3
- "version": "1.11.0",
3
+ "version": "1.12.0",
4
4
  "description": "Read-only Salesforce security audit for the sf CLI: 88 checks, attack-chain correlation, A-F risk grading, and compliance mapping to OWASP, SOC 2, ISO 27001, NZISM and more.",
5
5
  "keywords": [
6
6
  "salesforce",