San Francisco, California
ISO consultants for San Francisco software and AI companies.
California's frontier AI law covers only developers training the largest models, and it never names ISO/IEC 42001. For everyone else here, the pressure comes from customers, and the state privacy regulator's rules reach far more companies.
ISO certification consulting in San Francisco at a glance
- Who we are
- Glocal Insight: senior ISO management system consultants working with San Francisco companies on site and remotely. The consultant who scopes the work does the work.
- Standards
- ISO 9001, AS9100, ISO 14001, ISO 45001, ISO 27001, ISO 42001, ISO 13485, ISO 17025, plus internal audits, auditor training and ISO certification maintenance.
- Typical timeline
- For ISO 9001 at a company of 10 to 100 people, about three to four months from kickoff to the Stage 2 audit. Week by week.
- Cost
- A standalone gap analysis is typically in the low five figures; full implementation depends on scope. Certification body fees are separate. How certification costs are set, or estimate your audit days.
- Track record
- 100% certification success. 100% of surveyed clients would recommend us.
- Contact
- (816) 535-0738 or start a conversation.
California wrote a frontier AI law. It does not name ISO 42001.
The San Francisco metro has 3,398 manufacturing establishments, 3,173 of them with fewer than 100 employees (US Census County Business Patterns, 2023, San Francisco-Oakland-Fremont MSA). But much of this metro sells software, and the question software companies bring about ISO standards has changed. It is no longer only how they protect customer data. It is how they govern the AI in their product.
California has answered part of that question in law. The Transparency in Frontier Artificial Intelligence Act, SB 53, was signed on September 29, 2025, and took effect on January 1, 2026. The American Enterprise Institute describes it as the first law governing frontier AI safety in force anywhere in the United States.
It reaches far fewer companies than its reputation suggests. SB 53 applies to frontier developers: companies that have trained a foundation model using more than 1026 computing operations. Its main governance duty, publishing a frontier AI framework, applies only to large frontier developers, those with more than $500 million in annual gross revenue together with their affiliates.
And it does not name ISO/IEC 42001. The framework must describe how the developer incorporates “national standards, international standards, and industry-consensus best practices”, and the statute names none of them. For every software company in this metro, frontier developers included, ISO/IEC 42001 is not a legal requirement. It answers a different question, and enterprise customers are the ones asking it.
Industry in San Francisco
- Frontier AI developers SB 53 applies to developers that have trained a foundation model on more than 10^26 operations; only those with over $500 million in annual revenue must publish a frontier AI framework
- AI and machine learning startups The Governor's office reports that more than half of global venture funding for AI and machine learning startups went to Bay Area companies in 2024
- Salesforce, San Francisco Headquartered in Salesforce Tower; enterprise software, where ISO/IEC 27001 and 42001 questions arrive through customer security reviews
- Lam Research, Fremont Semiconductor equipment maker headquartered in Alameda County, inside this metro rather than the San Jose metro
- Businesses in scope for CCPA cybersecurity audits First audit reports due April 1, 2028 for in-scope businesses with more than $100 million in 2026 revenue, under the California Privacy Protection Agency's regulations
What SB 53 requires, and of whom
Every frontier developer must publish a transparency report before, or at the same time as, deploying a new or substantially modified frontier model. It covers the developer's website and contact route, the model's release date, supported languages, output modalities, intended uses and any general restrictions on use.
Large frontier developers carry more. They must write, implement, comply with and publish a frontier AI framework covering ten subjects, among them catastrophic-risk thresholds and assessments, mitigations, review before deployment, use of third-party assessors, cybersecurity for unreleased model weights, response to critical safety incidents and internal governance. Their transparency reports must also summarize their catastrophic-risk assessments and the part third-party evaluators played.
A critical safety incident must be reported to the state Office of Emergency Services within 15 days of discovery, or to an appropriate authority within 24 hours where it poses an imminent risk of death or serious physical injury. Only the Attorney General can enforce it: a large frontier developer that breaks these rules faces civil penalties of up to $1 million per violation.
The thresholds may change. The California Department of Technology must recommend, on or before January 1, 2027 and every year after, whether the definitions of frontier model, frontier developer and large frontier developer should change.
Where ISO/IEC 42001 fits
For a large frontier developer, ISO/IEC 42001 is one international standard it could describe incorporating into its framework. The statute does not prefer it, and a certificate is not compliance with SB 53. The framework's central subject, catastrophic risk from frontier models, is one the statute defines in its own terms.
For everyone else, which is nearly every software company here, the case is commercial. Enterprise procurement teams, security reviews and supplier assessments ask how a vendor governs the AI it ships, and an accredited certificate answers in a form those reviewers already recognize.
What the certificate stands for is a working system: an AI policy and defined roles, an inventory of the AI systems in scope, risk and impact assessments completed before a system goes live, a reasoned choice among the Annex A controls, and an independent auditor who has seen those controls operating. Our ISO 42001 and AI laws tracker covers the EU AI Act, Texas, Colorado and federal policy; California's position is set out on this page.
The California rules that reach far more companies
The California rule that will reach more San Francisco companies than SB 53 is not an AI statute. It is the regulation package of the California Privacy Protection Agency, now styled CalPrivacy, on automated decisionmaking technology, risk assessments and cybersecurity audits, which took effect on January 1, 2026.
A business that uses automated decisionmaking technology to make significant decisions about consumers must meet the ADMT requirements from January 1, 2027. Required risk assessments began on January 1, 2026, and an attestation and summary are due to the agency by April 1, 2028. An ISO/IEC 42001 impact assessment process is a natural home for that work, though meeting the regulation is a separate question.
Cybersecurity audits arrive in revenue tiers. A business in scope must complete its first audit report by April 1, 2028 if its 2026 revenue was over $100 million, by April 1, 2029 if its 2027 revenue was $50 million to $100 million, and by April 1, 2030 if its 2028 revenue was under $50 million. In scope means a business that meets the CCPA revenue threshold and processed the personal information of 250,000 or more consumers or households, or the sensitive personal information of 50,000 or more, in the preceding year, or one that earns half or more of its revenue from selling or sharing personal information.
Two clauses matter for an ISO/IEC 27001 program. The auditor must follow procedures and standards accepted in the auditing profession, and the regulation names the International Organization for Standardization among the bodies that provide them, alongside the AICPA, the PCAOB and ISACA. And a business may use an audit prepared for another purpose if it meets every requirement of the article, on its own or with supplementation. The regulation's own example is the NIST Cybersecurity Framework 2.0. It does not name ISO/IEC 27001.
So an ISO/IEC 27001 audit is not automatically your CCPA cybersecurity audit. The article lists components the audit must assess where they apply, from phishing-resistant multi-factor authentication to encryption of personal information at rest and in transit, and an audit scoped for your certificate has to be checked against that list.
The manufacturing side of the metro
This is not only a software market. Lam Research, the semiconductor equipment maker, has its headquarters in Fremont, which is in Alameda County and therefore in this metro rather than the San Jose metro. Palo Alto, Mountain View and Cupertino, by contrast, are in Santa Clara County and belong to San Jose's.
The metro's 3,173 manufacturing establishments under 100 employees are the usual ISO 9001 buyers. Those that sell into semiconductor equipment should check one customer document before any quality clause: the responsible business code their customer flows down. We set out why on our San Jose page.
How we work with companies here
We work with San Francisco companies on site and remotely. We put the on-site days where they change the outcome: the scoping workshop, the first internal audit and the certification audits.
The first conversation is about scope: which products, which AI systems and which customer commitments the certificate has to cover. That decision sets the cost of everything after it, and it is where a combined ISO/IEC 27001 and 42001 system saves the most.
The consultant who scopes the engagement does the work. No handoff to a junior implementer after the sale.
100% certification success. Every client we have taken to a Stage 2 certification audit has been certified, with no major nonconformities. 100% of surveyed clients would recommend us. Every client who answered our client satisfaction survey said they would recommend Glocal Insight.
ISO standards we help San Francisco companies with
This page focuses on ISO 42001, and we can help San Francisco companies with any of the standards below. If you are deciding whether to bring in outside help, start with what an ISO consultant does, how fees work and when certification is worth it.
ISO 42001 in San Francisco
The San Francisco-Oakland metro has 5,609 software publishers and custom programming firms (BLS QCEW, 2024 annual averages). ISO/IEC 42001 is the management system standard for organizations that develop or use AI, and it fits alongside an existing ISO 27001 system. See which state AI laws reference it.
The focus of this page. ISO 42001 consultants →
ISO 9001 in San Francisco
The Bay Area's research labs buy instruments, reagents and consumables labeled for research use only. For the companies that make them, ISO 9001 fits as long as the product, and the way it is sold, stays on the research side. The San Francisco-Oakland metro has 3,398 manufacturing establishments, 3,173 of them with fewer than 100 employees (US Census County Business Patterns, 2023), and 2,736 durable-goods wholesalers (BLS QCEW, 2024 annual averages). ISO 9001 is the most widely held ISO management system certification and the base that AS9100, ISO 13485 and the other sector standards build on.
ISO 9001 in San Francisco: the full page → · Free ISO 9001:2026 gap analysis checklist · Free ISO 9001 internal audit checklist
ISO 27001 in San Francisco
California's privacy agency now requires annual cybersecurity audits of businesses whose processing presents significant risk, phased in from 2027. Work done for another audit can count, if it meets every requirement. The San Francisco-Oakland metro has 9,397 computer systems design, software publishing and hosting establishments (BLS QCEW, 2024 annual averages). Software publishing employment here runs about 3.3 times its national share. ISO 27001 is the internationally recognized certification for an information security management system, and a common answer to enterprise customers' security questionnaires.
ISO 27001 in San Francisco: the full page → · Free ISO 27001 internal audit checklist · ISO 27001 audit days calculator
ISO 14001 in San Francisco
San Francisco requires commercial buildings of 50,000 square feet or more to run on 100% renewable electricity by December 31, 2030, on top of annual benchmarking and energy audits every five years. The San Francisco-Oakland metro has 453 establishments in chemical, plastics and rubber, paper, primary metal, and metal coating and finishing manufacturing (BLS QCEW, 2024 annual averages), the industries where air, water and waste obligations tend to be heaviest. ISO 14001 gives a site one system for its permits, its environmental aspects and its customers' sustainability questionnaires.
ISO 14001 in San Francisco: the full page → · Free ISO 14001:2026 gap analysis checklist · Free ISO 14001 internal audit checklist
AS9100 in San Francisco
The San Francisco-Oakland metro has 38 aerospace product and parts establishments and 190 machine shops (BLS QCEW, 2024 annual averages). AS9100 adds aerospace requirements to ISO 9001, and it reaches machine shops and processors through the purchase orders of the aerospace companies they supply; distributors use AS9120.
ISO 45001 in San Francisco
The San Francisco-Oakland metro has 3,398 manufacturing establishments (US Census County Business Patterns, 2023) and 11,188 construction establishments (BLS QCEW, 2024 annual averages). ISO 45001 turns a safety program into a management system, with hazard identification, worker participation and incident follow-up that a customer, general contractor or insurer can check.
ISO 13485 in San Francisco
The San Francisco-Oakland metro has 262 medical equipment and electromedical device manufacturing establishments (BLS QCEW, 2024 annual averages). Medical equipment and supplies employment here runs about 1.5 times its national share. ISO 13485 is the quality management standard for medical devices, and since February 2, 2026 the FDA's Quality Management System Regulation incorporates it by reference.
ISO 13485 consultants → · Free ISO 13485 internal audit checklist · ISO 13485 audit days calculator
ISO 17025 in San Francisco
The San Francisco-Oakland metro has 124 testing laboratories (BLS QCEW, 2024 annual averages). ISO/IEC 17025 is the accreditation standard for testing and calibration laboratories, including in-house labs whose results customers or regulators rely on.
What an engagement covers
- AI system inventory and scoping A register of the AI systems you build, buy and embed, and a certification scope that matches what your customers are actually buying.
- ISO/IEC 42001 system build AI policy, roles, risk and impact assessment, Annex A control selection and the records an auditor will sample. See ISO 42001.
- ISO/IEC 27001 alongside it One management system carrying both standards, with shared internal audit and management review. See ISO 27001.
- CCPA cybersecurity audit mapping Your controls checked against the components the CPPA regulation lists, so one audit program serves both purposes where it legitimately can.
- SB 53 threshold reading SB 53 facts for your counsel
- Gap analysis and roadmap Two to four weeks, fixed scope and price, with a clear go or no-go before real money is committed.
- Internal audit and management review Auditor-grade internal audits and a facilitated management review producing recorded decisions.
Questions we get from companies in this market
Does California's SB 53 require ISO 42001 certification?
No. The Transparency in Frontier Artificial Intelligence Act asks large frontier developers to describe, in a published framework, how they incorporate national standards, international standards and industry-consensus best practices. It names no standard, and the text never mentions ISO/IEC 42001. A developer could cite 42001 as one of the international standards it uses. Holding the certificate is not compliance with the law. This is not legal advice; confirm with your counsel.
Is our San Francisco AI startup covered by SB 53?
Only if you have trained, or begun training, a foundation model using more than 10^26 computing operations, counting later fine-tuning. That makes you a frontier developer, which brings transparency reports and incident reporting. The published framework duty applies only if you are also a large frontier developer, with more than $500 million in annual gross revenue together with your affiliates. A company that only uses another developer's model, through an API for example, has not trained one; whether heavy fine-tuning changes that is a question for counsel. The Department of Technology will recommend by January 1, 2027 whether these definitions should change.
Will our ISO 27001 audit count as our CCPA cybersecurity audit?
Possibly, but not automatically. The CPPA regulation lets a business use an audit prepared for another purpose if it meets every requirement of the article, on its own or with supplementation, and it names the International Organization for Standardization among acceptable sources of audit procedures. But it lists specific components the audit must assess where they apply, such as phishing-resistant multi-factor authentication and encryption of personal information, and its own example of a reusable audit is the NIST Cybersecurity Framework 2.0. Check your audit's scope against that list. First reports are due April 1, 2028 for businesses with more than $100 million in 2026 revenue.
When do California's automated decisionmaking rules apply?
The CPPA regulations took effect on January 1, 2026. A business that uses automated decisionmaking technology to make significant decisions must comply with the ADMT requirements from January 1, 2027. Required risk assessments began on January 1, 2026, with an attestation and summary due to the agency by April 1, 2028.
Is ISO 42001 worth it if no law requires it?
Usually the deciding factor is your customers. Enterprise procurement and security reviews increasingly ask how a vendor governs AI, and an accredited certificate answers in a form they recognize. Our AI laws tracker sets out what certification does and does not prove.
Can ISO 27001 and ISO 42001 share one management system?
Yes, and for a software company that already holds ISO/IEC 27001 it is the efficient route. Both follow the same management system structure, so policy, roles, document control, internal audit and management review are shared. The AI-specific work, including the AI system inventory, impact assessments and the Annex A controls of 42001, is added to the system you already run rather than built beside it.