[{"data":1,"prerenderedAt":170},["ShallowReactive",2],{"publication:en:P088":3},{"meta":4,"copy":17,"relatedArticles":130,"terms":162,"term":163,"resourceParent":164,"glossaryParent":167},{"id":5,"path":6,"kind":7,"keyword":8,"title":9,"seoTitle":10,"description":11,"incoming":12,"updated":15,"preparedOn":16},"P088","\u002Fblog\u002Femployee-ai-data-policy","article","employee AI data policy for small business","Employee AI data policy for a small business","Employee AI data policy: tasks, tools and information","Build an employee AI data policy around approved tasks, accounts, information and connectors. Use synthetic examples and clear exception and reporting routes.",[13,14],"\u002Fservices\u002Fdigital-security","\u002Fservices\u002Faccess-2fa-audit","2026-08-21","2026-10-30",{"intro":18,"sections":19,"checklist":88,"faq":96,"links":106,"sources":123,"cta":125},"An employee AI data policy tells staff which business tasks they may perform with AI, which information they may provide, and which accounts and connections are approved. Start with the work and the minimum necessary input. A tool name, paid subscription or instruction to “be careful” cannot answer those questions on its own.",[20,26,58,68,76,82],{"title":21,"paragraphs":22},"Start with a business task that someone owns",[23,24,25],"Write one concrete use case before drafting a company-wide rule: preparing a reply outline, translating public product text or summarizing approved internal guidance. Identify who checks the result and where it will be used. Drafting a message and automatically sending it to a customer are different activities, even when the same application offers both.","Give employees a usable default. They can work with genuinely public material and invented examples within an approved workflow; nonpublic business information requires the appropriate review. State the escalation route in ordinary language, including who can decide when a deadline is close. A policy that nobody can apply during a normal workday will leave decisions to individual guesswork.","Keep this employee-facing rule separate from the technical design of an agent. Staff need to know what they may submit and publish. The administrator must separately control account ownership, connectors and actions. Record both responsibilities so a signed policy is not treated as evidence that the underlying permissions are correct.",{"title":27,"paragraphs":28,"table":31},"Classify the input before choosing the tool",[29,30],"For each task, list the information actually required. Public opening hours may be enough to draft a response template; a full support conversation usually includes far more. Consider customer identifiers, private commercial terms, staff details, screenshots, attachments and information about other parties embedded in an otherwise ordinary document.","Use a task card like the one below as an internal working aid. Its decisions are examples to adapt, not a universal authorization or legal classification. The important question is whether the intended result can be achieved with less information, a locally prepared summary or a synthetic sample. Never use real credentials, recovery codes or secret keys as demonstration material.",{"caption":32,"headers":33,"rows":37},"Employee task and information approval card",[34,35,36],"Task","Minimum useful input","Decision to record",[38,42,46,50,54],[39,40,41],"Draft a public FAQ","Approved public product facts","Approved account; human checks facts before publication",[43,44,45],"Prepare a support reply structure","Invented request with no customer history","Use a synthetic sample; employee writes the real final response",[47,48,49],"Summarize internal operations","Only the specifically reviewed document or extract","Owner approves information class, tool configuration and recipients",[51,52,53],"Analyze customer records","Purpose and fields established before any transfer","Pause until the responsible owner reviews terms, access and obligations",[55,56,57],"Connect a mailbox or CRM","Specific records and allowed operations","Separate connector approval from ordinary chat approval",{"title":59,"paragraphs":60,"sources":64},"Approve the account, plan, settings and connections together",[61,62,63],"Record the exact provider, business account owner, product or plan, relevant settings and review date. Check the terms and controls that apply to that particular use: input and output handling, retention, possible training use, administrator visibility, sharing and connected services. Do not infer these from a logo or assume every offering from one provider behaves identically.","A connector can change the approved task substantially. A user who may draft from public text does not automatically have approval to search the company drive, expose a mailbox or let an assistant write into a CRM. Check what the connection can read, which identity it uses and whether it can take actions. Review again when the product, configuration or intended use changes.","NIST’s July 2024 Generative AI Profile discusses acceptable-use governance, third-party assessment and data risks. Here, those principles become a practical approval record rather than a claim that a business has implemented or been certified against the whole framework. Product terms must be checked directly when a real tool is selected.",[65],{"label":66,"url":67},"NIST AI 600-1 (July 2024): generative AI governance and data risks","https:\u002F\u002Fnvlpubs.nist.gov\u002Fnistpubs\u002Fai\u002FNIST.AI.600-1.pdf",{"title":69,"paragraphs":70,"example":73},"Remove unnecessary context, not just a customer name",[71,72],"Replacing a name does not establish that a document is anonymous. A rare incident, order reference, email signature, embedded screenshot or combination of details may still identify a person or reveal confidential work. Review the whole input and any output destined for another audience. Where the task allows, start from an invented example instead of editing a live record.","Also check how people transfer material. A screenshot can include browser tabs or a notification. A copied conversation can include quoted replies and internal notes. A folder connection can expose records beyond the one document the employee intended to use. The employee should be able to explain both the intended input and the actual route by which it reaches the tool.",{"title":74,"text":75},"Illustrative example: a useful reply without a customer export","A coordinator wants a polite response for a delayed website project. Instead of uploading the customer mailbox, they create a fictional scenario containing only a generic delay, an agreed next step and a neutral tone. The tool drafts a structure. The coordinator supplies verified project details in the approved business system and checks the final message. This is a proposed workflow, not a customer case or proof that any particular provider is approved.",{"title":77,"paragraphs":78},"Teach staff how to review output and report a mistake",[79,80,81],"Require a named person to check factual claims, links, calculations, tone and inappropriate disclosure before material is sent or published. A confident answer can still be wrong. A summary of a supplier document must not be treated as fresh authorization to change bank details, share a file or alter account access. Those actions keep their existing verification process.","Give employees a short reporting path for an accidental upload or unexpected connection. Ask for the tool and account, approximate time, categories of information involved and whether sharing or actions occurred. Do not ask them to paste the sensitive material into a second unapproved channel. The responsible owner can then coordinate containment, evidence preservation and any provider-specific options.","Avoid promising that deleting a chat erases every retained copy or that an account setting settles all contractual obligations. Record what has been checked, what remains uncertain and who will follow up. A useful report distinguishes a suspected disclosure from a confirmed recipient or action.",{"title":83,"paragraphs":84},"Maintain a policy that follows the actual business",[85,86,87],"Assign an owner, review trigger and accessible version of the policy. Include new staff, agency workers and people using personal accounts for business. Review when a connector is added, a team adopts a new workflow or a provider changes relevant terms. Keep exceptions narrow, recorded and time-bounded rather than silently making them the new default.","CyberFixCrew is an Israeli cybersecurity company serving businesses worldwide. Our practical Israeli website and digital-infrastructure perspective connects this policy to account ownership, access controls and the systems staff already use. Start a scoped discussion with the task, tool and information categories, without sending customer records or credentials. Technical review and the business owner’s policy decisions have distinct responsibilities.","For a first rollout, choose one useful task, train a small authorized group and check whether people can follow the rule without workarounds. Keep the result, limitations and open questions. Expand only when the ownership, information boundaries and review process are clear enough to maintain.",[89,90,91,92,93,94,95],"Name the business task and output reviewer.","List the minimum information and excluded sensitive material.","Record the approved provider, account, plan, settings and date.","Review connectors and actions separately from chat access.","Use a synthetic example to explain the everyday rule.","Define exceptions, accidental-upload reporting and ownership.","Review changes to tools, information, roles and connected systems.",[97,100,103],{"question":98,"answer":99},"Is a paid AI account automatically approved for customer information?","No: review the particular account, plan, configuration, terms, task and information involved. A payment does not determine the data-handling rules or authorize a connector.",{"question":101,"answer":102},"Can employees paste a document after removing the names?","Only after the actual information and workflow have been reviewed. Indirect identifiers, confidential context and attachments can remain. A fictional sample is often sufficient for drafting a structure.",{"question":104,"answer":105},"Does this policy replace access controls for an AI agent?","No, employee instructions and technical authorization serve different purposes. Tools, identities, records, actions and revocation require their own enforced controls.",[107,110,113,116,119,121],{"path":108,"label":109},"\u002Fblog\u002Fprompt-injection-business","Understand why source material must not grant authority",{"path":111,"label":112},"\u002Fblog\u002Fai-agent-permissions","Review AI agent tools and connected permissions",{"path":114,"label":115},"\u002Fblog\u002Fbusiness-data-map","Map business information before approving a new route",{"path":117,"label":118},"\u002Fblog\u002Fvendor-access-review","Review supplier access and responsibility",{"path":13,"label":120},"Discuss business digital-security scope",{"path":14,"label":122},"Review account access and authentication",[124],{"label":66,"url":67},{"title":126,"description":127,"button":128,"type":129},"Make AI use fit your business information boundaries","Describe the task, tool, account ownership and information categories. CyberFixCrew can discuss the connected account and digital-infrastructure controls without receiving a customer-data export.","Discuss account and information boundaries","check",[131,139,147,154],{"id":132,"path":108,"title":133,"description":134,"category":135,"artwork":136,"order":137,"publishedOn":138},"P089","Prompt injection risks for business: separate content from authority","Understand prompt injection in business AI workflows. Map untrusted content, connected data and action controls without relying on prompts alone.","governance","security",76,"2026-08-07",{"id":140,"path":141,"title":142,"description":143,"category":135,"artwork":144,"order":145,"publishedOn":146},"P091","\u002Fblog\u002Fsmall-business-asset-inventory","Digital asset inventory for small business: owners and dependencies","Map domains, websites, email, hosting, integrations and recovery owners. Build a useful inventory without storing passwords or losing business dependencies.","servers",92,"2026-09-04",{"id":148,"path":111,"title":149,"description":150,"category":135,"artwork":151,"order":152,"publishedOn":153},"P090","AI agent permissions for business: control tools, data and actions","Review AI agent tools, identities, read access and business actions. Define approval, logs and a shutdown route before connecting customer systems.","access",68,"2026-07-22",{"id":155,"path":156,"title":157,"description":158,"category":135,"artwork":159,"order":160,"publishedOn":161},"privacy-regulation","\u002Fblog\u002Fcyber-regulation-privacy-compliance-website-checklist","Website Privacy Checklist for a Technical Review","A technical website privacy review maps collected data, recipients, access rights, retention and deletion. First have an adviser determine the requirements that apply to your organization, then compare settings and test results with those requirements. The resulting evidence supports a wider assessment; it is not a legal compliance certificate.","plan-plus",100,"2026-05-05",[],null,{"path":165,"label":166},"\u002Fresources","Website security resources and templates",{"path":168,"label":169},"\u002Fglossary","Cybersecurity glossary for small businesses",1794134059373]