Cyber insurance renewal requirements for Houston businesses in 2026

Cyber Insurance Renewal Requirements for 2026: A Guide for Houston Businesses

Cyber insurance renewal requirements are becoming increasingly important for small and midsize businesses. As cyberattacks grow more sophisticated, insurance companies are examining cybersecurity controls more closely before issuing or renewing policies.

For Houston businesses, this means that simply having antivirus software and a backup system may no longer satisfy an insurer’s expectations.

Instead, insurance applications may ask detailed questions about multi-factor authentication (MFA), endpoint detection and response (EDR), managed detection and response (MDR), immutable backups, and incident response planning.

Furthermore, insurers may request documentation showing that these security measures are actually implemented.

Consequently, businesses that prepare early may be better positioned to address underwriting questions, negotiate coverage, and reduce cybersecurity risks.

In this guide, Graphene Technologies explains the security controls insurers commonly evaluate, why renewal applications have become more detailed, and how Houston businesses can prepare for their next cyber insurance renewal.

Why Cyber Insurance Renewal Requirements Are Changing

Cyber insurance has evolved considerably in recent years.

Previously, some insurance applications relied heavily on basic questions about antivirus protection, backups, and general cybersecurity practices.

However, major cyber incidents have demonstrated that organizations can suffer substantial losses even when they have some security measures in place.

As a result, insurers have placed greater emphasis on verifying how businesses protect critical systems and respond to attacks.

Several high-profile incidents illustrate these concerns.

The MOVEit Supply Chain Breach

In 2023, attackers exploited a vulnerability in the MOVEit Transfer file-sharing platform.

Consequently, numerous organizations experienced data exposure through software used to exchange sensitive information.

The incident demonstrated how vulnerabilities in third-party applications can affect businesses that otherwise maintain strong internal security.

According to Cybersecurity Dive’s MOVEit breach timeline, the attack affected organizations across multiple industries.

The lesson for businesses: Cybersecurity assessments should include critical vendors, software dependencies, and third-party access.

The Change Healthcare Ransomware Attack

In February 2024, Change Healthcare experienced a major cyberattack that disrupted healthcare payment and claims-processing systems.

As a result, healthcare providers, pharmacies, and patients experienced significant operational consequences.

The incident also highlighted the importance of strong authentication, business continuity planning, and recovery capabilities.

HIPAA Journal’s coverage of major healthcare breaches provides additional context about the incident.

For healthcare organizations, the lesson is particularly important.

Even when patient records remain protected, an interruption to critical technology services can disrupt business operations.

The Arup Deepfake Financial Fraud

Another significant incident involved engineering company Arup.

In 2024, a finance employee was deceived through a fraudulent video conference involving AI-generated impersonations of company executives.

The incident resulted in approximately $25 million in fraudulent transfers.

As reported by Fortune, the case demonstrated how sophisticated impersonation techniques can undermine traditional payment-approval processes.

Consequently, organizations should evaluate their financial verification procedures alongside their technical cybersecurity controls.

Although these incidents do not establish universal insurance requirements, they illustrate the types of risks that insurers increasingly consider during underwriting.

1. Immutable Backups and Disaster Recovery Requirements

One of the most important cyber insurance renewal requirements involves data backup and recovery.

Most businesses already perform backups.

However, having backups does not necessarily mean the organization can recover successfully from ransomware.

For example, attackers may compromise administrator accounts and attempt to delete or encrypt backup copies before disrupting production systems.

Therefore, insurers may ask whether backup data is protected against unauthorized modification or deletion.

What Is an Immutable Backup?

An immutable backup is a protected copy of data that cannot be modified or deleted during a defined retention period under the applicable storage controls.

For example, some cloud backup systems use object-lock or write-once-read-many technology to prevent changes during the configured retention period.

Additionally, organizations may maintain offline or isolated backup copies.

These approaches help reduce the risk that an attacker can compromise both production systems and recovery data.

The CISA StopRansomware Guide recommends maintaining protected backups and testing recovery procedures.

What Insurers May Ask

Depending on the carrier and policy, a renewal application may request information about:

  • Backup frequency.

  • Immutable or offline backup storage.

  • Backup retention periods.

  • Separation of backup administration credentials.

  • Protection against unauthorized deletion.

  • The date of the most recent restoration test.

  • Documented disaster recovery procedures.

Furthermore, insurers may distinguish between a backup system and a tested recovery capability.

For example, a company may perform daily backups without ever verifying that critical systems can be restored.

Consequently, the organization could discover recovery problems only after a ransomware incident.

How Houston Businesses Should Prepare

First, confirm that critical business data is backed up.

Next, determine whether those backups are protected from unauthorized modification or deletion.

Additionally, perform a documented restoration test.

Finally, identify how long the business can operate without its most important systems.

Graphene Technologies helps organizations evaluate backup and recovery strategies through its backup and disaster recovery solutions.

Key takeaway: A successful backup job is not the same as a successful recovery. Therefore, businesses should regularly test their ability to restore operations.

2. Multi-Factor Authentication Requirements

Multi-factor authentication is another major consideration during cyber insurance underwriting.

MFA requires users to verify their identity through more than one authentication factor.

For example, an employee might enter a password and then complete an authentication challenge using a security key or authenticator application.

Consequently, an attacker who steals only the employee’s password may still be unable to access the account.

However, insurers may want to know exactly where MFA is enforced.

Which Systems Should Have MFA?

Businesses should evaluate MFA protection for:

  1. Microsoft 365 and business email accounts.

  2. Virtual private network connections.

  3. Remote desktop and remote-access services.

  4. Administrator and privileged accounts.

  5. Critical cloud applications.

  6. Supported privileged service-account workflows.

Importantly, traditional service accounts do not always support interactive MFA.

Therefore, organizations should use appropriate alternatives, such as managed identities, certificate-based authentication, restricted privileges, and other supported security controls.

Are All MFA Methods Equally Secure?

No.

Although SMS authentication offers more protection than passwords alone, it is generally less resistant to phishing and certain account-takeover techniques than phishing-resistant authentication methods.

For example, FIDO2 security keys and appropriately configured passkeys can provide stronger protection against credential-phishing attacks.

Furthermore, Microsoft Authenticator number matching helps reduce certain MFA prompt-abuse risks.

However, number matching does not eliminate every phishing technique.

Therefore, businesses should consider stronger authentication for administrators, finance employees, and executives.

Preparing for Insurance Renewal

Before completing an application, verify which systems require MFA and whether enforcement is consistent.

Additionally, document any exceptions and the controls used to address them.

If an application asks whether MFA is enabled for all remote access, do not answer yes unless the statement accurately reflects your environment.

Key takeaway: MFA should be consistently implemented, verified, and documented rather than assumed to be active.

3. Endpoint Detection and Response: EDR vs. MDR

Traditional antivirus software remains useful.

However, modern cybersecurity threats often require more advanced detection and response capabilities.

Consequently, cyber insurance applications may ask whether a business uses Endpoint Detection and Response or Managed Detection and Response.

What Is EDR?

Endpoint Detection and Response monitors activity on devices such as workstations and servers.

Unlike traditional signature-based antivirus tools, EDR can provide additional behavioral detection, investigation, and response capabilities.

For example, EDR may identify suspicious processes, unusual system activity, or behavior associated with ransomware.

Furthermore, some EDR platforms allow security teams to isolate compromised devices.

However, detecting a threat does not guarantee that someone will respond promptly.

What Is MDR?

Managed Detection and Response combines security technology with an external team that monitors, investigates, and responds to threats under an agreed service scope.

For example, an MDR provider may investigate suspicious activity outside normal business hours.

Depending on the service agreement, the provider may also initiate containment or coordinate remediation.

Therefore, MDR can be particularly valuable for small and midsize businesses without dedicated cybersecurity personnel.

EDR vs. MDR Comparison

Security capability EDR MDR
Endpoint threat detection Yes Typically included or integrated
Behavioral monitoring Yes Yes
Threat investigation Internal team or provider Managed security team
Security alert monitoring Requires assigned responsibility Included according to service scope
Incident response assistance Depends on configuration and team Typically included within agreed scope
Best suited for Organizations with response resources Businesses needing managed security expertise

What Insurers May Evaluate

Insurers may ask whether:

  • EDR covers company workstations.

  • Servers are included in monitoring.

  • Security alerts are investigated.

  • Monitoring occurs outside business hours.

  • Incident response procedures are documented.

  • The organization uses a managed security provider.

However, the precise requirements vary by insurer.

Therefore, businesses should review the actual application rather than assuming MDR is mandatory for every policy.

Graphene Technologies provides managed security services to help Houston businesses strengthen threat detection, monitoring, and response capabilities.

Key takeaway: Security tools are most effective when someone is responsible for investigating and responding to their alerts.

4. Privileged Access Management and Administrator Security

Administrator accounts represent a particularly important cybersecurity risk.

These accounts may have permission to modify systems, create users, access sensitive information, and change security configurations.

Consequently, compromised administrator credentials can allow attackers to cause extensive damage.

For this reason, insurers may ask about privileged access management.

What Is Privileged Access Management?

Privileged Access Management, commonly called PAM, refers to technologies and processes used to secure elevated access.

For example, PAM solutions may provide:

  • Privileged credential vaulting.

  • Controlled administrator access.

  • Credential rotation.

  • Session monitoring.

  • Access approval workflows.

  • Privileged activity logging.

Additionally, businesses should limit the number of employees with administrative privileges.

Why Shared Administrator Accounts Are Risky

Suppose five employees use the same administrator account.

If suspicious activity occurs, identifying the responsible individual may be difficult.

Furthermore, a compromised shared password could expose multiple systems.

Instead, businesses should use individually attributable administrator accounts wherever practical.

They should also enforce appropriate authentication, logging, and least-privilege access.

Key takeaway: Administrator access should be restricted, monitored, and periodically reviewed.

5. Wire Transfer Verification and AI Deepfake Protection

Cybersecurity insurance is not limited to ransomware and data breaches.

Business email compromise and fraudulent financial transfers can also create substantial losses.

Furthermore, AI-generated voice and video impersonation have introduced additional challenges.

For example, a fraudulent request may appear to come from a company executive or trusted vendor.

Consequently, employees should not rely solely on email, caller ID, or video appearances when approving sensitive transactions.

Establish a Written Wire Transfer Policy

Businesses should consider implementing a formal payment-verification process.

For example, a policy might require:

  • Independent verification of new payment instructions.

  • Callbacks using previously verified contact information.

  • Dual approval for transactions above a defined threshold.

  • Additional verification for changes to vendor banking details.

  • Employee training on impersonation and deepfake risks.

  • Documentation of financial approvals.

Importantly, the verification phone number should come from a trusted existing record—not solely from the email requesting the payment.

Why Documentation Matters

An informal procedure may not provide the same assurance as a documented and consistently followed policy.

Therefore, businesses should establish written requirements and train employees responsible for financial transactions.

Additionally, organizations should review whether their cyber insurance policy includes social engineering or funds transfer fraud coverage.

Coverage may be subject to separate limits, conditions, or exclusions.

Key takeaway: Strong financial controls complement technical cybersecurity measures and help reduce fraud exposure.

6. Third-Party Vendor and Supply Chain Security

Many businesses rely on external software providers to operate.

For example, a Houston accounting firm may use cloud-based tax software, document management platforms, and payment-processing services.

Similarly, a manufacturing company may depend on inventory systems, production software, and external logistics platforms.

However, these vendors can introduce additional cybersecurity exposure.

Consequently, insurers may ask how organizations evaluate third-party security.

Questions to Ask Critical Vendors

Businesses should identify their most important technology vendors and determine:

  1. What sensitive information does the vendor access or store?

  2. Does the vendor provide a SOC 2 Type II report or another relevant security assessment?

  3. How does the vendor protect customer information?

  4. What happens if the vendor experiences a cyberattack?

  5. Does the vendor have documented incident response procedures?

  6. How quickly will the vendor notify customers about a security incident?

Furthermore, organizations should review vendor access when contracts end.

Although not every insurer requires formal SOC 2 reports from every vendor, maintaining a risk-based vendor review process demonstrates stronger cybersecurity governance.

Key takeaway: Businesses should understand their critical technology dependencies and the security risks associated with them.

7. Why Accurate Cyber Insurance Applications Matter

One of the most important steps in cyber insurance renewal is answering the application accurately.

For example, an application may ask whether MFA protects every administrator account.

If MFA is enabled for most accounts but not all, answering yes without qualification could create a problem.

Similarly, a business should not claim to have immutable backups if its backup system does not actually provide that protection.

What Is Cyber Insurance Policy Rescission?

Rescission is a legal remedy that may allow an insurer to treat a policy as void from its inception under applicable law.

However, rescission is not automatic whenever an application contains an error.

Whether an insurer can rescind a policy depends on the policy, the facts, the nature of the representation, and applicable state law.

In Texas, legal requirements governing insurance misrepresentations can be significant.

Therefore, businesses should consult their insurance broker or qualified legal counsel when questions arise about application disclosures or potential coverage disputes.

How to Avoid Application Errors

Before submitting the renewal application:

  • Review technical answers with your IT provider.

  • Verify security controls rather than relying on assumptions.

  • Identify exceptions or incomplete deployments.

  • Maintain documentation supporting material representations.

  • Ask your insurance broker how to disclose unresolved gaps.

  • Confirm that answers reflect the application’s specific wording.

Furthermore, avoid describing planned security improvements as though they are already operational.

Instead, disclose their current status and expected completion dates when the application allows.

Key takeaway: Accurate documentation and transparent communication are essential parts of cyber insurance preparation.

8. A 30-Day Cyber Insurance Renewal Checklist

Businesses approaching renewal should begin preparing as early as possible.

However, even a focused 30-day review can identify important gaps.

Week 1: Review Identity and Access Security

First, verify MFA across email, remote access, and privileged accounts.

Next, review administrator permissions and identify unnecessary access.

Additionally, document any exceptions requiring remediation.

Goal: Understand and improve identity-security controls.

Week 2: Verify Backups and Recovery

Review backup schedules, retention policies, and storage protections.

Furthermore, confirm whether backup copies are immutable, offline, or otherwise isolated.

Next, conduct a restoration test and document the results.

Goal: Demonstrate that critical information can be recovered.

Week 3: Evaluate Endpoint Security and Vendors

Confirm EDR coverage across supported workstations and servers.

Additionally, determine who monitors security alerts and how incidents are escalated.

Meanwhile, identify critical third-party vendors and request available security documentation.

Goal: Establish visibility into endpoint protection and third-party risks.

Week 4: Review Incident Response and Insurance Documentation

Update the organization’s incident response plan.

Then, conduct a tabletop exercise involving relevant management and technical personnel.

For example, simulate a ransomware incident affecting a critical business application.

Afterward, document lessons learned and assign follow-up responsibilities.

Finally, review the insurance application with your IT provider and broker.

Goal: Submit accurate information supported by documented security practices.

Importantly, a 30-day review may not be sufficient to resolve every issue.

Nevertheless, it can establish a remediation plan and help management understand the organization’s current cybersecurity posture.

9. How Graphene Technologies Helps Houston Businesses Prepare for Cyber Insurance Renewal

Preparing for cyber insurance renewal often requires coordination between business owners, insurance brokers, and IT professionals.

However, many small and midsize organizations do not have internal cybersecurity teams capable of reviewing every technical requirement.

That is where Graphene Technologies can help.

We support Houston businesses through managed IT and cybersecurity services designed to strengthen security and improve operational resilience.

Our services include:

  • Managed IT services and infrastructure management.

  • Cybersecurity assessments.

  • Endpoint security and threat monitoring.

  • Managed Detection and Response solutions.

  • Identity and access security.

  • Microsoft 365 security management.

  • Backup and disaster recovery planning.

  • Network security assessments.

  • IT consulting and cybersecurity improvement planning.

Furthermore, our team can help businesses identify technical gaps relevant to questions on their cyber insurance applications.

For example, we can evaluate MFA implementation, endpoint protection, backup capabilities, and monitoring arrangements.

Additionally, we can help develop a prioritized remediation plan based on the organization’s needs.

Explore Graphene Technologies’ managed security services and network security solutions to learn more.

Although Graphene can assist with technical assessments, insurance coverage decisions and policy interpretations remain the responsibility of insurers, brokers, and qualified insurance or legal professionals.

Frequently Asked Questions About Cyber Insurance Renewal Requirements

What are the most common cyber insurance renewal requirements?

Cyber insurance applications frequently evaluate MFA, backup and recovery capabilities, endpoint protection, remote access security, and incident response procedures. Additionally, some insurers ask about privileged access management, vendor security, and financial fraud controls.

However, requirements vary by insurer, business size, industry, and policy.

Is MFA required for cyber insurance?

Many insurers place significant emphasis on MFA, especially for email, remote access, and administrator accounts.

Nevertheless, whether MFA is mandatory depends on the specific underwriting requirements.

Businesses should review their application carefully and verify where MFA is enforced.

What is the difference between EDR and MDR?

EDR is a technology used to detect and investigate suspicious endpoint activity.

In contrast, MDR is a managed security service that provides threat monitoring, investigation, and response under an agreed service scope.

Therefore, MDR can be useful for businesses without dedicated security personnel.

Do cyber insurance companies require immutable backups?

Some insurers specifically ask about immutable, offline, or otherwise protected backups.

However, requirements vary by policy.

Regardless of insurance requirements, protected backups and tested recovery procedures are important cybersecurity safeguards.

Can cyber insurance be denied because of missing security controls?

Yes. An insurer may decline coverage, impose conditions, adjust pricing, or apply exclusions based on its underwriting criteria.

However, the outcome depends on the insurer and the organization’s risk profile.

Can an inaccurate cyber insurance application affect a future claim?

Yes. Material inaccuracies may create coverage disputes and, under certain circumstances, support legal remedies such as rescission.

Nevertheless, the legal outcome depends on applicable law, policy terms, and the facts involved.

Therefore, businesses should verify their answers and seek professional advice when necessary.

How early should businesses prepare for cyber insurance renewal?

Ideally, organizations should begin reviewing security requirements at least 60–90 days before renewal.

However, the appropriate timeline depends on the complexity of the environment and the improvements required.

Starting early provides more time to address security gaps.

Prepare Your Houston Business for Cyber Insurance Renewal

Cyber insurance renewal is more than an administrative task.

It is also an opportunity to evaluate how effectively your business protects its systems, employees, and critical information.

By reviewing MFA, implementing appropriate endpoint protection, strengthening backup systems, and documenting incident response procedures, organizations can improve their cybersecurity readiness.

Furthermore, these improvements provide value beyond insurance compliance.

They help reduce operational risk, strengthen business continuity, and support long-term growth.

Graphene Technologies helps Houston businesses evaluate cybersecurity controls and prepare for technical questions associated with cyber insurance renewal.

Whether your business needs a security assessment, managed threat detection, backup improvements, or ongoing IT support, our team can help identify practical next steps.

Schedule a Cybersecurity Assessment

Contact Graphene Technologies to discuss your organization’s cybersecurity needs.

Phone: 713-574-7200
Website: graphenetechs.net

 

Microsoft 365 Copilot security and data protection for Houston businesses

Microsoft 365 Copilot Security: What Businesses Must Check Before Deployment

Microsoft 365 Copilot security should be a priority for every business planning to introduce artificial intelligence into its daily operations. Although Copilot can improve productivity, summarize meetings, analyze documents, and streamline workflows, it can also reveal information that employees already have permission to access—even when those permissions are broader than intended.

For Houston businesses, this creates an important challenge. Over time, Microsoft 365 permissions often become difficult to manage. Employees change departments, project teams expand, and external sharing links remain active long after they are needed.

Consequently, introducing Copilot without reviewing those permissions can make existing data-sharing problems more visible.

Fortunately, businesses can reduce these risks before deployment.

In this guide, Graphene Technologies explains how Microsoft 365 Copilot accesses business information, why oversharing happens, and which security controls organizations should review before launching an AI pilot.

How Microsoft 365 Copilot Accesses Your Business Data

Microsoft 365 Copilot uses Microsoft Graph and other Microsoft 365 services to retrieve relevant organizational information.

Depending on the user’s permissions, licensing, and enabled capabilities, Copilot can work with information from:

  • SharePoint documents and libraries.

  • OneDrive files and shared folders.

  • Microsoft Teams conversations and files.

  • Outlook emails and calendar information.

  • Meeting transcripts and other supported Microsoft 365 content.

Importantly, Copilot is designed to respect the signed-in user’s existing access permissions.

According to Microsoft’s guidance on establishing a secure and governed Copilot environment, organizations should prepare their data governance and security controls before deployment.

However, respecting existing permissions does not automatically mean those permissions are appropriate.

For example, an employee may still have access to confidential financial documents from a project completed two years ago.

Although the employee no longer needs that information, the access permission may remain active.

As a result, Copilot could potentially retrieve relevant information from those documents when responding to an authorized user’s request.

The primary concern is not that Copilot ignores permissions. Instead, it is that existing permissions may already be too broad.

Why Microsoft 365 Permissions Become a Security Risk

Most businesses do not intentionally give employees excessive access to confidential information.

Nevertheless, permission problems often develop gradually.

For example, consider a Houston professional services firm with 75 employees.

Initially, the company creates separate SharePoint sites for accounting, operations, human resources, and client projects.

However, as the business grows, employees begin requesting additional access.

A manager might share a financial report with another department. Similarly, an employee may create a Teams channel for a temporary project.

Meanwhile, external consultants receive access to documents needed for specific assignments.

Unfortunately, those permissions are not always removed when projects end.

Over several years, the company may accumulate:

  • Former employees’ accounts with unnecessary access.

  • Confidential documents shared with large groups.

  • External sharing links without appropriate expiration controls.

  • Teams channels containing sensitive information.

  • SharePoint sites with outdated membership.

  • Financial documents stored in broadly accessible folders.

Consequently, employees may retain access to information unrelated to their current responsibilities.

Before implementing Copilot, businesses should identify and correct these issues.

Graphene Technologies helps organizations address these challenges through managed IT services in Houston, including Microsoft 365 administration, security reviews, and ongoing technology management.

Five Examples of Microsoft Copilot Data Oversharing Risks

Understanding the risks becomes easier when considering realistic business situations.

The following examples are hypothetical. However, each illustrates how excessive permissions could affect Copilot responses.

1. Confidential Employee Salary Information

Suppose an HR manager shares a compensation spreadsheet with a department supervisor.

Later, that supervisor changes roles, but the document permissions remain unchanged.

If the supervisor still has access, Copilot may be able to reference the spreadsheet when answering a relevant question.

Therefore, businesses should restrict compensation documents to authorized HR and executive personnel.

2. Sensitive Client Documents

Consider an accounting firm that creates SharePoint folders for individual clients.

During a temporary project, an employee receives access to several confidential files.

However, the company never removes those permissions.

Consequently, Copilot may surface information from those documents when the employee asks questions related to the client.

This creates unnecessary confidentiality exposure.

3. Financial and Business Development Information

Sales forecasts, acquisition plans, pricing strategies, and financial projections frequently reside in Microsoft 365.

Furthermore, employees may share these documents across departments for legitimate business reasons.

Over time, those permissions can become broader than necessary.

As a result, Copilot may consolidate information from multiple accessible sources into a single response.

Although the underlying documents were already accessible, the information may become easier to discover.

4. Employee Performance and Termination Records

Human resources documents often contain highly sensitive personal information.

For example, performance evaluations, disciplinary records, and separation agreements may be stored in SharePoint or OneDrive.

If permissions are incorrectly configured, unauthorized internal access may already exist.

Therefore, organizations should carefully review HR document libraries before enabling Copilot.

5. Internal Pricing and Profit Margins

Many Houston businesses maintain confidential pricing models, supplier agreements, and profit-margin calculations.

However, these files sometimes remain in shared folders after employees finish reviewing them.

Consequently, users with unnecessary access may be able to retrieve information through Copilot that management intended to restrict.

The takeaway: Copilot can make existing information easier to find. Therefore, businesses should correct excessive permissions before introducing AI-powered search and summarization.

Why a Small Microsoft Copilot Pilot Still Requires Security Planning

Many organizations begin with a limited Copilot trial.

At first, this appears to be a low-risk approach.

After all, only a few employees receive licenses.

However, the number of users does not determine the entire risk.

Instead, the permissions assigned to those users are equally important.

For example, senior executives frequently have access to confidential financial reports, strategic plans, and sensitive employee information.

Consequently, a pilot involving three executives may expose a broader range of information than a pilot involving employees with more limited permissions.

Nevertheless, this does not mean businesses should avoid executive pilots.

Rather, organizations should evaluate each participant’s access before enabling Copilot.

Recommended Copilot Pilot Controls

Before launching a pilot:

  1. Identify the employees participating in the trial.

  2. Review their SharePoint and OneDrive permissions.

  3. Confirm access to sensitive Teams channels.

  4. Evaluate external sharing settings.

  5. Apply appropriate sensitivity labels.

  6. Establish acceptable-use and data-handling guidelines.

  7. Configure available monitoring and auditing capabilities.

Additionally, businesses should document which activities Copilot is expected to support.

For example, a pilot might focus on meeting summaries, document drafting, or internal knowledge retrieval.

By defining these objectives early, organizations can measure productivity improvements while controlling unnecessary exposure.

Four Microsoft 365 Security Audits to Complete Before Copilot Deployment

Microsoft provides guidance for preparing organizations to adopt Copilot securely.

In particular, its Copilot oversharing deployment blueprint addresses permission cleanup, security guardrails, and compliance considerations.

Although every organization has different requirements, four areas deserve particular attention.

1. Audit SharePoint Permissions

First, review how employees access SharePoint sites and document libraries.

Identify sites that contain confidential information, including financial reports, client records, and personnel documents.

Next, examine:

  • Site owners and members.

  • Broad access groups.

  • Organization-wide sharing permissions.

  • External guest access.

  • Inactive SharePoint sites.

  • Sensitive documents stored in shared libraries.

Additionally, organizations with access to the appropriate capabilities can use SharePoint Advanced Management to help identify oversharing risks.

Once the review is complete, remove unnecessary permissions and assign clear ownership.

Why this matters: Copilot relies on existing access controls. Therefore, reducing excessive SharePoint permissions also reduces the information unnecessarily available to users.

2. Review OneDrive External Sharing

Next, examine documents shared outside the organization.

OneDrive makes collaboration convenient. However, employees may forget to remove sharing permissions after projects finish.

For example, a consultant may receive access to a confidential spreadsheet during a short engagement.

Months later, the sharing link may remain active.

Therefore, organizations should review:

  • External sharing permissions.

  • Anonymous or broadly accessible links.

  • Guest access.

  • Sensitive documents shared with third parties.

  • Sharing-link expiration settings.

Additionally, administrators should establish appropriate policies for future external collaboration.

These controls can reduce accidental data exposure while preserving legitimate business workflows.

3. Audit Microsoft Teams Membership

Microsoft Teams is another important area to review.

Over time, Teams environments often accumulate inactive channels, temporary project members, and outdated guest accounts.

Furthermore, Teams files may be stored in associated SharePoint sites.

Consequently, administrators should evaluate both Teams membership and the underlying document permissions.

Start by identifying:

  • Teams containing confidential information.

  • External guests who no longer require access.

  • Employees assigned to outdated project groups.

  • Channels with unnecessarily broad membership.

  • Shared documents with inconsistent permissions.

Afterward, establish a recurring review process.

For Houston businesses using Teams extensively, ongoing Microsoft 365 management can help maintain appropriate access as employees and projects change.

4. Implement Microsoft Purview Sensitivity Labels

Finally, businesses should classify sensitive information.

Microsoft Purview sensitivity labels can help organizations identify and protect confidential content.

For example, a business might establish classifications such as:

  • Public.

  • Internal.

  • Confidential.

  • Highly Confidential.

Depending on configuration and licensing, labels can support encryption, access restrictions, and other data-protection policies.

Furthermore, appropriately configured Data Loss Prevention policies can restrict certain Copilot interactions with sensitive content.

Microsoft explains these capabilities in its guidance on Microsoft Purview and Copilot security.

However, applying a label does not automatically prevent Copilot from accessing a document.

Instead, protection depends on the policies, encryption settings, permissions, and usage rights associated with that label.

Therefore, organizations should test their configurations before relying on them to protect sensitive information.

How Long Does Microsoft 365 Copilot Security Preparation Take?

The preparation timeline depends on the organization’s size, data volume, licensing, and existing security practices.

For example, a business with 25 employees and well-managed SharePoint permissions may complete an initial review relatively quickly.

In contrast, a professional services firm with 150 employees, extensive external sharing, and several years of accumulated files may require a more substantial project.

Generally, the process includes four stages.

Stage 1: Discovery

First, identify sensitive data, current permissions, and existing sharing policies.

Stage 2: Risk Assessment

Next, prioritize excessive permissions, confidential information exposure, and outdated access.

Stage 3: Remediation

Afterward, correct permissions, implement appropriate labels, and configure security policies.

Stage 4: Pilot Validation

Finally, test Copilot with a limited group of users and confirm that sensitive information remains appropriately protected.

Importantly, businesses do not need to achieve perfect data governance before testing Copilot.

However, they should address material oversharing risks and establish appropriate safeguards before introducing the technology into sensitive workflows.

How Graphene Technologies Helps Houston Businesses Deploy Copilot Securely

Microsoft 365 Copilot can improve productivity. However, successful deployment requires more than purchasing licenses.

Businesses must also evaluate their data security, access permissions, and governance policies.

At Graphene Technologies, we help Houston organizations plan and manage secure Microsoft 365 environments.

Our services include:

  • Microsoft 365 administration and management.

  • Cloud security assessments.

  • Identity and access management.

  • SharePoint and Teams permission reviews.

  • Cybersecurity monitoring.

  • IT strategy and consulting.

  • Security policy and governance planning.

Furthermore, our managed security services help businesses strengthen their broader cybersecurity posture.

For organizations evaluating AI adoption, our IT consulting services in Houston can also support technology planning and implementation.

Additionally, businesses can review our related article, How to Prepare Microsoft Copilot Without Exposing Sensitive Business Data, for more guidance.

Five Questions to Ask Your IT Provider Before Enabling Copilot

Before purchasing Microsoft 365 Copilot licenses, ask your IT provider these questions:

  1. Have we reviewed SharePoint permissions and identified overshared files?

  2. Do we know which confidential documents are accessible to broad employee groups?

  3. Have we reviewed external sharing in OneDrive and Teams?

  4. Are sensitivity labels and appropriate data-protection policies configured?

  5. Do we have a plan to monitor and govern Copilot usage?

If your provider cannot answer these questions, consider completing a Microsoft 365 security assessment before deployment.

After all, introducing AI should improve business productivity—not increase unnecessary data exposure.

Frequently Asked Questions About Microsoft 365 Copilot Security

Is Microsoft 365 Copilot secure for small businesses?

Microsoft 365 Copilot includes enterprise security and permission-based access controls. However, its security also depends on how the organization configures Microsoft 365. Therefore, businesses should review permissions, identity controls, and data governance before deployment.

Can Microsoft Copilot access confidential company files?

Copilot can use supported content that the signed-in user is authorized to access. Consequently, confidential files with unnecessarily broad permissions may appear in responses to users who retain that access.

Does Microsoft Copilot bypass SharePoint permissions?

No. Microsoft 365 Copilot is designed to respect existing permissions. However, those permissions may be broader than the organization intends. Therefore, a SharePoint access review is essential.

Can Microsoft Purview sensitivity labels protect Copilot data?

Yes, when appropriately configured. For example, encryption and supported Data Loss Prevention policies can restrict access or processing. However, simply applying a sensitivity label does not automatically block Copilot.

Should businesses audit Microsoft 365 before enabling Copilot?

Yes. A permissions and data-governance review can identify unnecessary access, external sharing risks, and confidential information that requires additional protection.

How can a Houston IT provider help with Copilot deployment?

A qualified provider can review Microsoft 365 permissions, assess security risks, recommend governance controls, and help establish a controlled pilot. Additionally, ongoing IT management can support security as the organization expands its AI usage.

Prepare Your Houston Business for Microsoft 365 Copilot

Microsoft 365 Copilot offers valuable opportunities to improve efficiency, collaboration, and decision-making.

However, businesses should understand how their information is accessed before introducing AI-powered tools.

By reviewing SharePoint permissions, controlling external sharing, evaluating Teams membership, and implementing appropriate data-protection policies, organizations can reduce unnecessary exposure.

Furthermore, ongoing cybersecurity monitoring and access reviews help maintain those improvements over time.

Graphene Technologies helps Houston businesses strengthen Microsoft 365 security and prepare for responsible AI adoption.

Whether your organization is considering its first Copilot pilot or expanding an existing deployment, our team can help identify security gaps and establish practical next steps.

Schedule a Microsoft 365 Security Assessment

Contact Graphene Technologies or call 713-574-7200 to discuss your Microsoft 365 environment.

 

Ransomware attacks on small businesses and cybersecurity protection in Houston

How Ransomware Attacks Small Businesses: A Week Inside a Cyberattack

Ransomware attacks on small businesses can begin long before anyone sees a ransom note. An employee receives a convincing email, a stolen password is reused, or an attacker gains access to a Microsoft 365 account. By the time the business notices unusual activity, sensitive information may already be exposed.

For Houston businesses with 10 to 200 employees, the consequences can include interrupted operations, lost revenue, compromised customer information, and costly recovery efforts.

But how does an attack actually unfold?

Let’s follow a fictional 22-employee Houston commercial services company through one possible ransomware attack. The scenario combines known cybercriminal tactics into a single illustrative timeline. It is not a documented incident or a prediction of how every attack occurs.

Along the way, we’ll identify five opportunities to interrupt the attack using practical security controls.

Monday: How Attackers Identify a Small Business

The first step in many cyberattacks is reconnaissance.

Attackers can gather publicly available information about an organization without accessing its internal systems.

For example, a Houston contractor may have:

  • Business registration information available through public databases.

  • Employee names and job responsibilities listed on LinkedIn.

  • Customer relationships or project announcements on its website.

  • Job advertisements revealing commonly used business software.

  • Contact details published on social media or professional directories.

Individually, these details may seem harmless. Together, they can help an attacker identify employees with access to financial systems, customer information, or administrative accounts.

In our example, the attacker discovers that the company’s office manager handles payroll, supplier payments, and administrative tasks.

That employee becomes a potential target.

The business lesson: Cybersecurity awareness should include the information employees and organizations publish publicly. The goal is not to eliminate a professional online presence, but to understand how information can be combined and misused.

Tuesday: Building a Picture of the Organization

The attacker continues researching the company.

Public employee profiles reveal who works in accounting, operations, and management. Job advertisements suggest the company uses Microsoft 365 and accounting software.

The attacker now has enough context to make a fraudulent message sound credible.

Rather than sending an obvious generic phishing email, the attacker can reference a familiar supplier, a business process, or a technology platform employees regularly use.

This is one reason phishing remains dangerous even when employees receive security awareness training.

A convincing message may appear to be directly related to someone’s job.

How Graphene Technologies helps

Effective defense combines employee education with technical safeguards.

Graphene’s managed security services help Houston businesses strengthen their security posture through monitoring, threat detection, and response.

Security training remains important, but employees should not be the only line of defense.

Wednesday: Stolen Credentials Create an Opening

The attacker obtains credentials associated with the company’s email domain.

Stolen credentials can originate from previous data breaches, info stealer malware, phishing, or password reuse.

In this fictional scenario, an employee has reused a password previously exposed through an unrelated service.

That creates an opportunity for an attacker to attempt unauthorized access.

Even if the password no longer works, exposed credentials can provide clues about account naming conventions or password habits.

What businesses should do

Start with several practical controls:

  1. Require unique passwords for every business account.

  2. Use an approved password manager.

  3. Monitor for exposed corporate credentials.

  4. Disable unused accounts promptly.

  5. Apply strong authentication policies to sensitive systems.

Businesses can also use Have I Been Pwned to investigate whether email addresses have appeared in known breaches. A breach listing does not automatically mean an account is currently compromised.

Microsoft Entra password protection and related identity-security policies can help reduce weak-password risk, but password controls should be combined with phishing-resistant authentication and monitoring.

For Houston organizations without dedicated security staff, Graphene’s endpoint security services can provide another layer of protection against malware and suspicious endpoint activity.

Thursday: The Microsoft 365 Account Is Compromised

The attacker attempts to access the office manager’s Microsoft 365 account.

Fortunately, the organization uses multi-factor authentication (MFA).

That makes a simple stolen-password attack harder.

However, not every form of MFA provides the same protection.

Some sophisticated phishing attacks can trick users into authenticating through a fraudulent sign-in experience and expose reusable session information.

These are commonly described as adversary-in-the-middle (AiTM) attacks.

Microsoft Authenticator’s number-matching functionality helps address certain MFA prompt-abuse techniques, but number matching alone does not eliminate phishing or session-theft risks.

In our scenario, the attacker gains unauthorized access to the employee’s account and begins examining business communications.

How to strengthen Microsoft 365 security

Organizations should evaluate:

  • Phishing-resistant MFA, including appropriate passkeys or FIDO2 security keys.

  • Microsoft Entra Conditional Access policies where supported by licensing.

  • Device compliance and managed-device requirements.

  • Suspicious sign-in detection and investigation.

  • Protection against malicious inbox rules and unauthorized forwarding.

  • Rapid account and session revocation procedures.

These controls work best as part of a layered identity-security strategy.

Graphene Technologies helps Houston organizations assess and strengthen their Microsoft 365 environment as part of broader managed cybersecurity services.

Friday: A Business Disruption Becomes a Ransomware Incident

The attacker has access to an employee account and potentially sensitive business communications.

Those communications may reveal upcoming projects, financial information, customer relationships, and operational deadlines.

In the fictional scenario, the attacker later obtains additional access to company systems and deploys ransomware.

Employees suddenly cannot access shared files or important business applications.

Customer projects are delayed, invoices cannot be processed, and management must determine how to restore operations.

The incident is no longer simply an IT problem.

It has become a business continuity crisis.

Why backups alone are not enough

A company may have automated backups and still experience a prolonged outage.

Recovery depends on several factors:

  • Whether clean backup copies exist.

  • Whether attackers could access or modify those backups.

  • How quickly critical systems can be restored.

  • Whether recovery procedures have been tested.

  • Whether the organization has an incident response plan.

Graphene’s backup and disaster recovery solutions help Houston businesses protect critical data and plan for operational recovery.

A successful backup is valuable. A tested recovery plan is what helps restore business operations.

Five Security Controls That Could Interrupt This Attack

The fictional attack illustrates several opportunities to reduce the likelihood or impact of compromise.

1. Strengthen Identity and Password Security

Unique passwords, password managers, account lifecycle management, and credential-exposure monitoring reduce risks associated with reused or compromised credentials.

2. Implement Phishing-Resistant MFA

Traditional MFA is better than password-only authentication, but phishing-resistant methods provide stronger protection against certain credential and session-interception attacks.

High-risk users—including executives, finance employees, and administrators—should receive priority.

3. Restrict External Email Forwarding

Unauthorized forwarding rules can expose sensitive business communications.

Microsoft documents how administrators can configure external email forwarding restrictions.

Businesses should also monitor suspicious inbox rules and investigate unexpected mailbox access.

4. Monitor and Respond to Security Alerts

A security alert only creates value when someone reviews it and takes appropriate action.

Organizations should understand which alerts their tools generate, who receives them, and how incidents are escalated.

This is an important reason to consider managed security services in Houston when internal IT teams cannot provide consistent security oversight.

5. Prepare for Recovery Before an Incident

Maintain protected backup copies, test restoration procedures, document critical systems, and assign responsibilities for incident response.

The CISA StopRansomware Guide provides additional guidance for ransomware prevention, response, and recovery.

Businesses should also consider network security measures such as segmentation and secure remote access to help limit unauthorized movement between systems.

Three Questions Every Houston Business Should Ask Its IT Provider

If your business uses Microsoft 365, cloud applications, or shared business systems, ask your IT provider:

1. Are our most sensitive accounts protected by phishing-resistant MFA?

Finance, administrator, and executive accounts often deserve stronger controls.

2. Are external forwarding and suspicious mailbox rules restricted and monitored?

An attacker who gains mailbox access may attempt to collect information without immediately disrupting operations.

3. Who monitors our security alerts, and what happens when a threat is detected?

Confirm who is responsible, when monitoring occurs, and how incidents are escalated.

If your provider cannot clearly answer these questions, a security review may be worthwhile.

Frequently Asked Questions

Do ransomware attackers target small businesses?

Yes. Small businesses can be targeted through phishing, credential theft, vulnerable systems, and other methods. Attackers may view organizations with limited cybersecurity resources as attractive opportunities, although businesses of all sizes face ransomware risk.

What is an adversary-in-the-middle phishing attack?

An AiTM phishing attack can intercept an authentication process and potentially expose session information. Depending on the security controls in place, attackers may use that information to gain unauthorized account access.

What are stealer logs?

Stealer logs are collections of information obtained by infostealer malware. They may contain credentials, browser data, or authentication information that criminals attempt to misuse.

Can Microsoft 365 Business Premium help protect against ransomware?

Microsoft 365 Business Premium includes security capabilities that can support endpoint protection, identity security, and threat detection. However, specific features depend on licensing, configuration, and the services being used. No single license or security product guarantees ransomware prevention.

Can a business recover from ransomware without paying?

Recovery may be possible through protected backups, restoration procedures, and incident response. The outcome depends on the scope of compromise, availability of clean recovery points, and whether information was stolen as well as encrypted.

Protect Your Houston Business Before a Cyberattack

Ransomware prevention is not simply about buying more cybersecurity software.

It requires the right combination of identity protection, employee awareness, endpoint security, monitoring, network controls, and tested recovery procedures.

At Graphene Technologies, we help Houston businesses strengthen cybersecurity while keeping their IT environments manageable and productive.

Whether you need ongoing threat monitoring, Microsoft 365 security improvements, endpoint protection, or disaster recovery planning, our team can help you evaluate your current environment and identify practical improvements.

Ready to understand your cybersecurity exposure?

Contact Graphene Technologies to discuss your business security needs.

Call: 713-574-7200

Business WiFi security and guest network protection in Houston

Guest Wi-Fi Security: How Houston Businesses Should Separate Their Networks

Offering Wi-Fi to customers, vendors, contractors, and visitors is convenient. However, giving guests internet access should not give their devices access to your business network.

A visitor’s phone or laptop may be perfectly safe. On the other hand, it could be outdated, infected with malware, or poorly secured. Because your business does not manage that device, you have limited control over its security.

That’s why properly configured guest Wi-Fi is an important part of network security for Houston businesses.

A secure guest network should allow visitors to access the internet while preventing them from reaching business computers, servers, network printers, file storage, backup systems, security cameras, access-control systems, and network equipment.

Most importantly, having two different Wi-Fi names does not necessarily mean you have two properly separated networks.

What Is a Secure Guest Wi-Fi Network?

A properly configured guest Wi-Fi network gives visitors internet access while isolating them from your company’s internal systems.

For example, your network might be organized like this:

Business Network → Computers, servers, printers, and business applications

Guest Network → Internet access only

Both networks can still use the same internet connection. Therefore, most businesses do not need a second internet circuit simply to provide guest Wi-Fi.

Instead, the separation occurs inside your network infrastructure. Your firewall, router, switches, and wireless access points determine which devices can communicate with each other.

Why Should Houston Businesses Separate Guest Wi-Fi?

Connecting a visitor to the same network as your employees does not automatically give that visitor access to every company file. After all, passwords, permissions, and endpoint security still provide protection.

However, a device on the same network may be able to discover or communicate with systems it has no reason to access.

For example, those systems could include a printer, shared folder, network storage device, security camera, server, or poorly protected network-management interface.

Additionally, an infected device can attempt to communicate with other systems on the network. Network segmentation reduces this exposure because it limits which devices and networks are allowed to communicate with each other.

For a business, the principle is simple:

A customer’s phone doesn’t need to communicate with your accounting computer, so your network shouldn’t allow it.

Two Wi-Fi Names Don’t Necessarily Mean Two Separate Networks

This is one of the first things businesses should check.

For instance, you might see:

ABC Company

and

ABC Company Guest

These are different Wi-Fi network names, also known as SSIDs. Nevertheless, creating a second SSID does not guarantee that devices on the two networks are properly isolated.

The configuration behind those Wi-Fi names is what matters.

Typically, business networking equipment uses a VLAN (Virtual Local Area Network) for guest traffic. Firewall rules can then prevent devices on that VLAN from accessing your private business networks.

Depending on your equipment, you may see settings such as Guest Network, Network Isolation, Deny Local Network Access, Client Isolation, VLAN, or Guest Firewall Rules.

Therefore, if your current setup consists of little more than a second Wi-Fi name and password, ask your IT provider to verify whether actual network isolation exists behind it.

What Is a VLAN?

A VLAN allows your business to logically separate devices even when they share some of the same physical networking equipment.

For example, an office could use:

VLAN 10 — Business computers

VLAN 20 — Guest Wi-Fi

VLAN 30 — Security cameras

VLAN 40 — IoT and smart devices

From there, the firewall establishes rules that determine which networks can communicate.

For instance:

Guest Wi-Fi → Internet: ALLOW

Guest Wi-Fi → Business computers: BLOCK

Guest Wi-Fi → Security cameras: BLOCK

Guest Wi-Fi → Network management: BLOCK

As a result, visitors can use your internet connection without receiving unnecessary access to internal company resources.

Should Guest Devices Be Able to See Each Other?

Usually, they should not.

In addition to separating guests from your business network, you can prevent one visitor’s device from communicating directly with another visitor’s device.

Depending on the networking equipment, this feature may be called client isolation, wireless isolation, peer-to-peer blocking, or Layer 2 isolation.

It’s also important to understand that client isolation and network segmentation serve different purposes. Client isolation prevents Guest A from communicating with Guest B. In contrast, network segmentation prevents guests from communicating with your company’s internal systems.

Therefore, a properly configured business guest network will generally use both controls.

Where Should Employees’ Personal Phones Connect?

Employee-owned phones that only need internet access can generally use a guest or another appropriately restricted network.

Similarly, a personal laptop that does not require access to internal company resources may belong on a restricted network rather than your main business network.

However, the situation changes when employees use personal devices to access company files, applications, or internal systems.

In that case, your organization should have a defined Bring Your Own Device (BYOD) policy covering permitted access and minimum security requirements.

For example, those requirements might include device encryption, supported operating systems, security software, MFA, or device management.

Ultimately, an employee-owned device should not automatically receive unrestricted network access simply because the person works for your company.

What About Security Cameras, TVs, and IoT Devices?

Guest Wi-Fi isn’t the only network you may want to separate.

Modern businesses increasingly use internet-connected devices such as security cameras, smart TVs, digital signage, speakers, thermostats, access-control systems, conference-room equipment, and printers.

Many of these devices need internet access. However, they usually do not need unrestricted communication with employee computers.

For this reason, your IT provider may create a separate IoT VLAN or another restricted network.

The appropriate configuration depends on how each device operates. For example, a security camera may need to communicate with a local recorder, whereas a smart television may only need internet access.

Separating these devices can reduce unnecessary communication between systems and make network access easier to control.

5 Things to Check on Your Business Guest Wi-Fi

If you’re unsure whether your Houston office’s guest network is actually secure, start with these five checks.

1. Check Which Devices Use Each Network

First, determine which devices are connected to your business network.

Business-owned and managed computers should use the appropriate internal network. Meanwhile, visitors and unmanaged personal devices should generally use a restricted network.

2. Confirm Guests Cannot Reach Internal Devices

Next, connect a test device to your guest Wi-Fi.

Try to determine whether it can access printers, file storage, servers, cameras, or network-management pages. Ideally, those internal resources should not be accessible from the guest network.

In other words, don’t assume the network is isolated simply because it has a different Wi-Fi name. Test the actual access.

3. Enable Client Isolation

Additionally, check whether guest devices can communicate with one another.

If your equipment supports client or wireless isolation, consider enabling it for the guest network. As a result, one visitor’s device will have less opportunity to communicate directly with another visitor’s device.

4. Review Wi-Fi Security

Next, review the security configuration supported by your wireless equipment and devices.

Your guest network should also have a different password from your business Wi-Fi. Otherwise, sharing the guest password could expose credentials that are also used by company equipment.

5. Update Your Network Equipment

Finally, make sure your firewall, wireless access points, switches, and routers are running supported firmware.

You should also replace default administrator credentials and retire networking equipment that no longer receives security updates.

Whenever a firewall, router, switch, or wireless access point is replaced or substantially reconfigured, test your network segmentation again.

Do You Need Two Internet Connections?

In most cases, no.

A properly designed business network can use one internet connection while maintaining multiple isolated networks.

For example:

Internet
↓
Business Firewall
↓
Business VLAN | Guest VLAN | Camera/IoT VLAN

The firewall then controls what each network is permitted to access.

Additionally, your IT provider can apply bandwidth limits to guest Wi-Fi. Consequently, visitor traffic is less likely to consume bandwidth needed for VoIP calls, video meetings, cloud applications, and other business services.

Older or very basic networking equipment may not provide adequate segmentation controls. Therefore, businesses using older hardware should verify what their equipment actually supports.

Don’t Share Your Business Wi-Fi Password With Visitors

Your guest and business Wi-Fi should use different passwords.

Once the business password is given to visitors, contractors, or former employees, controlling future access becomes more difficult.

By comparison, a separate guest password can be changed without reconnecting every company-owned device.

However, remember that a guest password and network segmentation solve different problems.

A guest password controls who can connect. Network segmentation controls what they can access.

Your business needs both.

Frequently Asked Questions

Is a Guest Wi-Fi Password Enough to Protect My Business?

No. A password determines who can connect to the wireless network. However, your networking equipment must also prevent guest devices from communicating with internal business systems.

Can Guests and Employees Use the Same Internet Connection?

Yes. Both networks can share the same internet connection while remaining logically separated by your firewall and networking equipment.

Should Employees Put Their Personal Phones on Guest Wi-Fi?

If a personal phone only needs internet access, a guest or other restricted network is generally preferable to giving an unmanaged device access to the internal business network.

However, devices that need access to company resources should follow your organization’s BYOD and security policies.

Should Security Cameras Be on a Separate Network?

Often, yes. Security cameras and other IoT devices may have different access requirements from employee computers.

For example, cameras may need access to a local recorder while having no reason to communicate with an employee’s workstation. Therefore, the appropriate network design depends on your camera system, recorder, cloud services, and other infrastructure.

Does Guest Wi-Fi Prevent Cyberattacks?

No. Network segmentation is only one layer of security.

Businesses still need secure firewall policies, MFA, endpoint protection, software updates, backups, email security, and appropriate access controls.

Nevertheless, segmentation can reduce unnecessary access and limit which systems a compromised device can reach.

Is Your Houston Business Wi-Fi Actually Secure?

Seeing “Guest” in your Wi-Fi name doesn’t tell you whether the network is properly isolated.

Instead, ask a more important question:

What can a device connected to that network actually reach?

Graphene Technologies helps Houston businesses design and manage secure business networks, including firewalls, business Wi-Fi, VLANs, network segmentation, cybersecurity, and ongoing IT support.

If you’re unsure whether visitors, employee-owned devices, cameras, and business computers are properly separated, we can review your current network configuration.

Schedule a Free 30-Minute IT Assessment

We’ll review your current IT and network environment and identify security, configuration, and infrastructure issues that may deserve attention.

Cloud migration services for Houston businesses

Canceling a Cloud Service? How Houston Businesses Can Avoid Losing Data

Businesses change cloud services all the time.

You may replace a CRM, accounting platform, file-sharing service, project management system, email provider, or other SaaS application because you’ve found a better product, reduced costs, consolidated vendors, or changed IT providers.

Canceling the subscription may seem like the easy part.

Getting your company’s data out safely is the part that deserves attention.

A cloud service may contain years of customer records, emails, documents, invoices, project history, attachments, and employee activity. If you cancel before properly migrating that information, employees could lose access before your business has a usable copy. Pasted text

For Houston businesses moving from one cloud platform to another, a successful migration should include more than downloading a few files.

Here’s what to check before clicking Cancel.

What Happens to Your Data When You Cancel a Cloud Service?

There isn’t one universal answer.

Depending on the provider and subscription, cancellation could:

  • Prevent employees from signing in
  • Make applications read-only
  • Leave information accessible only to administrators
  • Begin a temporary retention period
  • Trigger eventual deletion
  • Continue billing through an existing contract term

The rules can also differ depending on whether you purchased the service directly from the software company, through a reseller, or through your IT provider.

For example, Microsoft 365 subscriptions move through different lifecycle stages after a subscription ends. Google also instructs Workspace customers to export information they want to retain before canceling.

Never assume your data will remain available for 30, 60 or 90 days.

Check the current rules for the specific service and contract you’re canceling.

1. Find Out Exactly What Happens After Cancellation

Before setting a cancellation date, determine:

When does employee access stop?

How long can administrators retrieve data?

When does deletion begin?

Can the account be reactivated?

When does billing actually stop?

Does the provider require an export request before cancellation?

If the answers aren’t clear in the provider’s documentation, contact the provider and get clarification in writing.

If your subscription was purchased through an MSP, IT provider or software reseller, have them confirm the process as well.

2. Identify Everything Stored in the Cloud Application

Don’t start by clicking Export.

Start by determining what you actually need to preserve.

Depending on the system, that might include:

  • Customer and vendor information
  • Documents
  • Email
  • Calendar information
  • Attachments
  • Invoices
  • Support tickets
  • Project history
  • Reports
  • Employee activity
  • Audit records
  • User permissions
  • Custom fields

One of the biggest cloud migration mistakes is assuming the provider’s standard export includes everything.

It may not.

Some exports contain the primary records but omit attachments, comments, permissions, deleted items, automation rules, application settings or activity history. Pasted text

3. Export Your Data Before You Cancel

Use a business-controlled administrator account to perform the export.

Don’t leave the only copy sitting in an employee’s Downloads folder or personal cloud account.

Instead, store the export in a secure location controlled by the business and make sure appropriate backups exist.

Large exports can also take time.

If your company has years of email, documents or customer information, don’t wait until the final afternoon of your subscription to begin.

Give your IT team enough time to investigate missing data, failed exports and unexpected file formats.

4. Test the Export Before Assuming You Have a Backup

Seeing a ZIP file or CSV in a folder doesn’t mean your data migration succeeded.

Open it.

Test samples of every important file type and verify:

  • Attachments are present
  • Dates are correct
  • Documents open properly
  • Customer information is complete
  • Historical records are available
  • Files can be associated with the correct customer or project

This becomes especially important with database-style applications.

A CSV might successfully export names and numbers while losing the relationships between records. Customers and invoices, for example, could appear in separate files without preserving how they were connected in the original system. Pasted text

An export that cannot be reconstructed or imported may not be particularly useful when you need it.

5. Test the New Cloud Platform Before Shutting Down the Old One

If you’re migrating to another service, don’t move everything at once.

Start with a small test.

Import representative data and have the employees who actually use the system verify it.

Check things such as:

Names → contacts → notes → dates → attachments → custom fields → tasks → permissions → historical transactions

Then test the actual workflow.

Can employees find customer information?

Do attachments open?

Are historical transactions attached to the right records?

Can the appropriate employees access what they need?

Only after the test works should you proceed with the larger migration.

6. Check Every Integration Before Canceling

This is one of the easiest things to overlook.

Cloud applications rarely operate completely by themselves.

Your website might send leads into a CRM. Your CRM might feed an email-marketing platform. Accounting software might receive invoices from another application.

Your old cloud service could be connected to:

  • Website forms
  • Microsoft 365
  • Accounting software
  • CRM systems
  • Email marketing
  • Payment systems
  • Calendars
  • Reporting platforms
  • Mobile applications
  • Automated workflows
  • APIs
  • Browser extensions
  • Cloud storage

Create a list of everything sending data into and receiving data from the old service.

Then migrate or disable those connections and test their replacements before cancellation. Pasted text

Otherwise, your migration might look successful while new leads, invoices or notifications quietly stop flowing.

7. Don’t Forget “Sign in With Microsoft” or “Sign in With Google”

This deserves special attention.

Employees sometimes use a company account to authenticate into unrelated applications through options such as:

Sign in with Microsoft

or

Sign in with Google

If that identity disappears during a Microsoft 365 or Google Workspace migration, employees could potentially lose access to connected applications too.

Before removing the original account, identify these dependencies and establish another approved authentication method where necessary.

Your business should also control administrator and recovery information for important applications.

After the migration is complete, revoke obsolete access tokens, API keys and application connections. Pasted text

8. Know Which Business Records You Need to Keep

Not every piece of information should simply be deleted when you leave a cloud provider.

Your organization may need to retain:

  • Financial records
  • Contracts
  • Customer communications
  • Employee records
  • Project documentation
  • Consent records
  • Transaction history

Retention requirements vary by industry, contract and jurisdiction.

Work with the appropriate accountant, attorney or compliance professional to determine how long specific records need to be maintained.

Your IT provider can then help make sure the required information is exported and stored securely.

9. Ask What the Cloud Provider Will Actually Delete

Canceling a subscription and deleting your company’s data aren’t necessarily the same event.

Ask the provider what happens to:

active data, deleted records, backups, audit logs, billing information, support tickets and account information.

Some information may disappear from active systems before copies age out of backups. Providers may also retain certain records for legitimate billing, fraud-prevention, security or legal purposes. Pasted text

For important systems, consider requesting written confirmation explaining what will be deleted, what will remain, and when deletion is expected to occur.

Cloud Service Cancellation Checklist

Before your Houston business cancels an important cloud or SaaS application:

1. Review the contract and cancellation policy.
Determine access, billing, retention and deletion dates.

2. Inventory the data.
Identify everything that needs to be retained or migrated.

3. Map integrations.
Document applications, APIs, website forms, automations and authentication dependencies.

4. Export the data.
Store it somewhere controlled by your business.

5. Verify the export.
Open files and check attachments, records and relationships.

6. Test the replacement system.
Import a sample and have actual users verify it.

7. Move integrations and employees.
Confirm normal business processes continue working.

8. Cancel the old subscription.
Save confirmation and final billing records.

9. Revoke obsolete access.
Remove users, integrations, tokens and API keys that are no longer required.

10. Confirm the provider’s deletion process.

That sequence is much safer than:

Cancel → Download → Hope everything transferred.

Frequently Asked Questions

How Long Does a Cloud Provider Keep Data After Cancellation?

There is no universal retention period.

It can depend on the provider, service, subscription, contract and how the service was purchased. Check the provider’s current documentation before canceling rather than relying on a general assumption. Pasted text

Is Exporting Cloud Data the Same as Backing It Up?

Not necessarily.

An export can provide a useful retained copy when it contains everything your business needs and can actually be opened or restored.

But some exports may exclude application settings, permissions, relationships, audit information or unsupported file types.

Always test an export before relying on it.

Can We Cancel Microsoft 365 and Still Retrieve Our Data?

Microsoft 365 business subscriptions have defined lifecycle stages after expiration or cancellation, but the exact circumstances can vary.

For a business migration, don’t rely on a post-cancellation recovery period as your migration strategy.

Export, back up and verify important information before cancellation.

Will Canceling a Cloud Subscription Stop Billing Immediately?

Not always.

Monthly subscriptions, annual commitments, fixed-term contracts and reseller agreements can have different billing rules.

Confirm both the final billing date and final service date before approving cancellation. Pasted text

Should an IT Provider Handle a Cloud Migration?

For a simple service containing little important data, internal staff may be able to handle it.

For business-critical systems involving Microsoft 365, email, customer records, authentication, integrations, large datasets or compliance requirements, having an IT provider plan and verify the migration can reduce the risk of lost data and unexpected downtime.

Planning a Cloud Migration for Your Houston Business?

Moving from one cloud service to another should not put years of company information at risk.

Graphene Technologies helps Houston businesses plan and manage cloud migrations, Microsoft 365 environments, backups, integrations and ongoing IT infrastructure.

Before canceling an important cloud platform, we can help determine what needs to be preserved, identify dependencies, test the migration and reduce the risk of business disruption.

Schedule a Free 30-Minute IT Assessment

We’ll review your current cloud and IT environment and help identify migration, backup, security or integration risks before they become problems.

AI phishing attacks targeting Houston businesses

AI Phishing Attacks: What Houston Businesses Need to Know

Yes. This one has good material, but I would reposition it around a stronger search phrase such as “AI phishing attacks” + “Houston businesses” and make the article lead naturally into Graphene’s cybersecurity services.

I also checked the underlying claims. The NCSC does specifically say generative AI can create convincing phishing lures without the translation, spelling, and grammatical mistakes that historically exposed them. The FBI likewise warns that criminals use generative AI to create believable spear-phishing and financial-fraud messages and reduce grammatical/spelling errors. National Cyber Security Centre

One correction: the 22,364 complaints / $893 million figure comes from the FBI’s 2025 IC3 report, not the older FBI alert linked in the original article. The 2025 report says AI-related information was reported in 22,364 complaints with adjusted losses exceeding $893 million. Internet Crime Complaint Center

Here is the version I’d publish.

AI Phishing Attacks: What Houston Businesses Need to Know

For years, one of the easiest ways to spot a phishing email was bad spelling.

Strange grammar, awkward sentences and obvious mistakes could quickly signal that an email claiming to be from your bank, supplier or CEO wasn’t legitimate.

AI is changing that.

Cybercriminals can now use generative AI to produce polished, professional-looking phishing emails in seconds. Messages can be personalized, grammatically correct and written in a tone that looks surprisingly similar to legitimate business communication.

For Houston businesses, that means employee phishing training needs to change too.

Instead of asking only, “Does this email look fake?”, employees increasingly need to ask:

“What is this email asking me to do?”

How AI Is Making Phishing Emails Harder to Spot

The UK’s National Cyber Security Centre (NCSC) has warned that generative AI can create convincing phishing material without many of the translation, spelling and grammatical errors that traditionally exposed phishing attempts. National Cyber Security Centre

The FBI has issued a similar warning.

According to the FBI, criminals are using generative AI to create believable content for social engineering, spear phishing and financial fraud. AI also allows criminals to produce messages faster, improve translations and eliminate language mistakes that might otherwise alert the recipient. Internet Crime Complaint Center

That changes what a modern phishing email can look like.

Instead of:

“Dear Customer, Your Account Have Been Suspended.”

an employee might receive a polished email that appears to come from a real supplier, references a plausible business situation and asks the accounting department to update payment information.

The writing may be perfect.

The request is the warning sign.

Why AI Phishing Can Be So Convincing

AI gives attackers several advantages.

The Writing Looks Professional

Generative AI can produce grammatically correct business emails in almost any tone.

An attacker no longer needs strong English-language skills to create a convincing email targeting a U.S. company.

Messages Can Be Personalized

Information about many businesses and employees is publicly available.

Company websites, LinkedIn profiles, press releases and social media can reveal employee names, job titles, suppliers, executives, projects and organizational relationships.

That information can potentially be incorporated into targeted social-engineering messages.

A finance employee could receive something that appears to be from an executive. A purchasing employee could receive what looks like a supplier request. An HR employee could receive a message appearing to come from another employee.

This type of targeted phishing is commonly called spear phishing.

Attackers Can Produce More Messages

AI also reduces the time required to create believable content.

The FBI says generative AI allows criminals to create messages faster and reach wider audiences with believable content. Internet Crime Complaint Center

The scale of AI-assisted fraud is already significant. The FBI’s 2025 Internet Crime Report recorded 22,364 complaints reporting AI-related information and more than $893 million in adjusted losses. Those figures cover AI-related cybercrime broadly rather than phishing alone, but they illustrate how AI has become part of the fraud landscape. Internet Crime Complaint Center

AI Phishing Isn’t Just an Email Problem

Generative AI can also be used for voice cloning, images and video.

The FBI warns that criminals can use AI-generated audio to impersonate relatives and other people, including creating audio that requests emergency financial assistance. It also describes AI-generated video being used to impersonate company executives and other authority figures. Internet Crime Complaint Center

For businesses, imagine receiving an urgent voicemail that appears to be from an executive:

“I need this wire processed before the end of the day. I’m heading into a meeting, so please handle it immediately.”

Recognizing the person’s voice should no longer be enough to override your company’s verification procedures.

Can Your Spam Filter Stop AI Phishing?

Modern email security remains an important part of protecting a business, but businesses shouldn’t assume that every fraudulent message will automatically be blocked.

A targeted social-engineering email doesn’t necessarily need malware or an obviously malicious attachment.

It could simply ask an employee to:

change payment instructions, send confidential information, log into an account, purchase gift cards, or call a fraudulent telephone number.

That’s why cybersecurity needs multiple layers: email security, identity protection, MFA, employee awareness and documented verification procedures.

7 Warning Signs Employees Should Look for Now

Perfect spelling doesn’t make an email trustworthy.

Teach employees to pay particular attention when a message:

  1. Requests money or a wire transfer.
  2. Changes supplier or customer bank information.
  3. Asks for a password, MFA code or other credential.
  4. Creates unusual urgency or pressure.
  5. Contains an unexpected attachment or link.
  6. Uses a familiar display name but an unfamiliar email address.
  7. Asks the employee to bypass a normal business procedure.

These signals focus on behavior and intent rather than grammar.

That distinction is increasingly important as AI-generated messages become more convincing.

How Houston Businesses Can Reduce AI Phishing Risk

Technology should be combined with clear procedures employees can actually follow.

Verify Payment Changes Outside Email

Create a simple rule:

Any request to change banking or payment information must be independently verified.

Call the supplier using a telephone number your company already has on record.

Don’t use the telephone number contained in the email requesting the change.

Use Phishing-Resistant MFA

MFA provides another layer of protection if an employee’s password is compromised.

But not all MFA methods provide the same protection.

CISA recommends businesses move toward phishing-resistant MFA and identifies security keys as offering particularly strong protection. CISA also recommends requiring MFA for systems such as email, file storage and remote access. CISA

For organizations using Microsoft 365, identity and MFA configuration should be an important part of the company’s overall Microsoft 365 security strategy.

Train Employees for Modern Phishing

Stop making bad grammar the centerpiece of phishing training.

Instead, teach employees to recognize:

unexpected requests + urgency + money + credentials + changes in normal procedure.

Give employees an easy way to report suspicious messages.

The objective isn’t to turn every employee into a cybersecurity expert. It’s to establish a predictable response when something unusual occurs.

Protect High-Risk Employees More Aggressively

Not every employee has the same risk.

Pay particular attention to accounts belonging to:

  • Owners and executives
  • Accounting and finance
  • HR
  • IT administrators
  • Employees authorized to make payments
  • Employees with access to sensitive customer information

A compromised accounting mailbox can have very different consequences from a compromised low-privilege account.

Create a Payment Verification Procedure

Technology can’t replace a good business process.

For example:

Email requests bank change → Employee calls known supplier contact → Change independently verified → Payment information updated

An “urgent” email from an executive shouldn’t bypass that process.

AI makes this procedure more important, not less.

What If an Employee Clicks a Phishing Link?

Speed matters.

Employees should immediately report the incident rather than trying to hide the mistake.

Depending on what occurred, your IT team may need to:

  • Reset the employee’s password
  • Revoke active sessions
  • Review sign-in activity
  • Investigate mailbox rules
  • Check for unauthorized account changes
  • Determine whether sensitive information was accessed
  • Review affected endpoints
  • Investigate other employees who received the same message

The earlier your IT provider knows about a suspected compromise, the sooner it can investigate and contain it.

Frequently Asked Questions

Can You Still Spot Phishing by Bad Spelling?

Sometimes, but it is no longer a reliable test.

The NCSC specifically warns that generative AI can produce phishing material without many of the spelling, grammatical and translation mistakes historically associated with phishing. National Cyber Security Centre

What Are the Biggest Phishing Warning Signs Today?

Focus on what the sender wants you to do.

Requests involving money, changed banking information, passwords, MFA codes, confidential information or unusual urgency deserve additional verification.

Also check the sender’s actual email address rather than relying solely on the displayed name.

Can AI Clone Someone’s Voice?

AI can generate audio that imitates another person. The FBI has warned that criminals use AI-generated audio to impersonate people and solicit payments. Internet Crime Complaint Center

Treat an unexpected voice request involving money or sensitive information the same way you would a suspicious email: independently verify it through a trusted channel.

Will Microsoft 365 Stop Every Phishing Email?

No security platform should be treated as a guarantee that every phishing message will be blocked.

Businesses should combine properly configured email security with MFA, identity controls, employee awareness, endpoint protection and procedures for sensitive financial requests.

Is MFA Enough to Stop Phishing?

MFA significantly strengthens account security, but the type of MFA matters.

CISA recommends moving toward phishing-resistant MFA and notes that traditional methods such as text/email codes provide weaker protection than stronger alternatives. CISA

Is Your Houston Business Prepared for AI Phishing?

AI has changed what a fraudulent email can look and sound like.

Your cybersecurity strategy needs to change with it.

Graphene Technologies helps Houston businesses protect Microsoft 365, email, endpoints, identities and company data against modern cybersecurity threats.

If you’re unsure whether your current email and Microsoft 365 security settings are properly configured, we’ll help you identify the gaps.

Schedule a Free 30-Minute IT Assessment

We’ll review your current IT and cybersecurity environment and identify areas that may leave your business exposed to phishing, account compromise and other threats.

BYOD security for Houston businesses

BYOD Security for Houston Businesses: How to Protect Company Data on Personal Devices

Employees using personal phones and laptops for work has become normal for many small and midsize businesses. An employee may add Microsoft 365 email to an iPhone, access company files from a home computer, join Teams meetings from a tablet, or download customer information to a personal laptop.

The convenience is obvious. The security risk is often less visible.

Once company information reaches a personal device, your business has less control over where that information is stored, which applications can access it, whether the device is properly updated, and what happens to the data if the employee leaves.

For Houston businesses using a Bring Your Own Device (BYOD) policy, the answer isn’t necessarily banning personal devices. The better approach is deciding what employees can access, which devices are permitted, and what security controls must be in place.

What Is BYOD?

BYOD stands for Bring Your Own Device. It refers to employees or contractors using personally owned phones, tablets, or computers for business.

That might include:

  • Accessing Microsoft 365 or Google Workspace
  • Adding company email to a personal phone
  • Opening customer or company documents
  • Using Teams, Zoom, Slack, or other business applications
  • Accessing CRM or accounting systems
  • Downloading files to a personal computer
  • Connecting to company cloud applications

The security issue isn’t simply who owns the device. It’s where your company’s data goes once that device is allowed access.

Why BYOD Can Create Security Risks for Houston Businesses

On a company-owned computer, your IT provider can control security settings, software, updates, encryption and access.

A personal device is different.

Employees may determine which applications are installed, when updates are performed, where files are backed up and whether other family members use the device. Even when management software is deployed, the level of control varies depending on the operating system and enrollment method. Pasted text

For a Houston SMB, several problems deserve particular attention.

 

1. Business Files Can End Up in Personal Storage

An employee downloads a customer spreadsheet from Microsoft 365.

Now that file might exist in:

Microsoft 365 → Downloads folder → personal cloud backup

Opening it in another application can create additional unmanaged copies.

Disabling the employee’s Microsoft 365 account later doesn’t necessarily remove those copies.

2. Personal Devices May Not Be Properly Updated

Your IT team may have limited visibility into whether an employee’s personal laptop is running a supported operating system or has current security patches.

An outdated personal computer accessing company email or cloud applications can introduce unnecessary risk.

3. Family Members May Share the Device

Home computers are frequently shared.

If an employee uses the same Windows or macOS account as a spouse or child, company files, saved browser sessions and other business information may become accessible to another person.

A BYOD policy should require separate user accounts and prevent access from devices where business information cannot be adequately separated from other users.

4. Personal Apps Can Interact With Business Information

Employees decide what software gets installed on their personal devices.

Some applications may have access to files, contacts, browser information or clipboard contents.

Without appropriate controls, your company may have little visibility into what happens to business information after it reaches that device.

5. Employee Offboarding Becomes More Complicated

Suppose an employee leaves your Houston business tomorrow.

Your IT provider can disable the employee’s Microsoft 365 account and revoke active sessions.

But what about files already downloaded to their personal laptop?

That is one of the biggest reasons businesses should establish BYOD controls before allowing employees to use personal devices.

7 BYOD Security Controls Houston Businesses Should Consider

A good BYOD strategy combines account security, device security and data protection.

1. Require Multi-Factor Authentication

MFA should be required for Microsoft 365, cloud storage and other important business applications.

MFA helps protect the user’s account if a password is compromised, but it doesn’t solve every BYOD problem.

A downloaded customer file, for example, still needs appropriate device and data protection.

2. Require Supported Operating Systems

Devices accessing company resources should run operating systems that still receive security updates.

Older devices that can no longer receive current security patches should not be allowed to access company information.

3. Require Device Encryption

Full-device encryption helps protect information stored on a laptop or phone if the device is lost or stolen.

Encryption should be enabled before the device disappears—not after an incident occurs.

4. Require Screen Locks

Require employees to protect devices with a strong PIN, password, fingerprint or facial recognition and configure automatic screen locking.

It’s a simple control, but an important one.

5. Use Approved Business Applications

Define which applications employees may use for:

email, messaging, file sharing, cloud storage, remote access and other company work.

Where possible, prevent company information from being copied into unmanaged applications or personal storage.

6. Consider Microsoft Intune and Application Management

For organizations using Microsoft 365, Microsoft Intune can help manage devices and protect company information.

Mobile Device Management (MDM) can apply policies to enrolled devices and determine whether they meet company security requirements.

Mobile Application Management (MAM) can protect information inside supported business applications without necessarily managing the employee’s entire personal device.

Depending on configuration, businesses can restrict copying, prevent saving information to personal locations and remove company information from managed applications when an employee leaves. The existing draft correctly distinguishes selective removal of managed company data from a full factory reset. Pasted text

7. Have a Lost-Device and Offboarding Process

Employees should know exactly who to contact when a device is:

lost, stolen, infected, replaced, repaired or sold.

Your IT team can then take appropriate steps such as revoking sessions, disabling access, removing managed company information and reviewing account activity.

The same process should be part of employee offboarding.

When Should Houston Businesses NOT Allow BYOD?

Personal devices aren’t appropriate for every employee or every type of work.

A company-owned, managed device is generally preferable when an employee:

  • Handles sensitive or regulated information
  • Has administrator privileges
  • Manages user accounts or security systems
  • Needs large amounts of company information stored locally
  • Shares the personal device with other people
  • Uses an unsupported operating system
  • Cannot enable encryption
  • Cannot keep company information separated from personal information

This is particularly important for administrators. Someone responsible for Microsoft 365 administration, backups, security settings or other critical business systems should perform that work from a managed company device, not an unmanaged home computer. Pasted text

What Should a BYOD Policy Include?

Your written BYOD policy should establish who can use personal devices, which devices are acceptable, what applications employees must use, whether files can be downloaded, required security settings, what your IT provider can manage, what happens when a device is lost, and how company information is removed when employment ends.

Employees should understand and accept these requirements before business access is provided. Pasted text

Is MFA Enough for BYOD Security?

No.

MFA protects the employee’s account. It doesn’t automatically protect information downloaded onto the device.

A more complete BYOD security strategy may include:

MFA + encryption + security updates + approved applications + access policies + MDM/MAM + documented offboarding procedures.

The appropriate combination depends on what information employees access and how they work.

Need Help Securing Personal Devices in Your Houston Business?

If employees are already checking company email, opening files or accessing Microsoft 365 from personal devices, you may already have a BYOD environment—even if your company has never formally created a BYOD policy.

Graphene Technologies helps Houston businesses secure Microsoft 365, endpoints, cloud applications and employee access.

We can review your current environment, identify where personal devices have access to company information, and recommend practical security controls without unnecessarily disrupting how your employees work.

Not sure whether your current setup is secure?

Schedule a Free 30-Minute IT Assessment

We’ll review your current IT and security environment and help identify areas that deserve attention.

 

Business website cybersecurity and protection concept for a Houston small business

Is Your Business Website a Security Risk? A Houston SMB Guide

Your website can become an overlooked security problem

A business website may run for months without anyone checking its security. However, websites need maintenance just like other technology.

Plugins become outdated. Administrator accounts remain active. In addition, backups may stop working without anyone noticing.

Attackers often scan many websites automatically. Therefore, they do not need to target your business by name to find a weakness.

Keep WordPress, plugins, and themes updated

WordPress sites depend on several software components. Each component can receive security updates.

Therefore, businesses should apply supported updates promptly. Delaying updates can leave a known weakness exposed.

However, do not update blindly on a critical website. Maintain a backup and test major changes when possible. That approach improves both security and reliability.

Protect administrator accounts

Website administrator accounts deserve strong protection because they can change the entire site.

First, give each administrator a separate account. Next, remove old developers, employees, and vendors who no longer need access.

Also, use strong unique passwords and MFA when available. Most importantly, avoid sharing one administrator password among several people.

Review forms and connected services

Contact forms often collect customer information. Some websites also connect to payment systems, email marketing platforms, or other business applications.

Therefore, review what information each form collects. Keep only what the business actually needs.

In addition, protect the accounts connected to those services. A secure website can still create risk if an integrated account has weak access controls.

Maintain a recovery plan

A website backup gives the business a way to recover after a bad update or security incident. However, a backup is useful only if it works.

Keep recent copies and understand how to restore them. Also, know who is responsible for the recovery process.

If an outside web developer manages the site, document that relationship. Your business should still know where the domain, hosting, DNS, and backups are managed.

Watch for signs of compromise

A hacked website does not always go offline. Instead, attackers may add hidden pages, redirects, spam, or malicious code.

Therefore, investigate unexpected website changes quickly. Also, pay attention to browser warnings and unusual search results.

Graphene Technologies helps Houston businesses review the security around websites, domains, DNS, accounts, backups, and connected systems. Schedule a free 30-minute IT assessment to identify technology and cybersecurity risks before they become larger problems.

Call to Action

Need a clearer picture of your IT risks and priorities? Schedule a Free 30-Minute IT Assessment with Graphene Technologies. We will review your current environment and identify practical next steps.

AI-powered phishing and scam email warning for a Houston business cybersecurity article

How Houston Businesses Can Spot AI-Powered Scam Emails

AI changed the look of phishing emails

For years, employees were told to look for spelling mistakes in scam emails. That advice is no longer enough.

AI tools can produce clear and professional messages in seconds. As a result, attackers can create emails that sound more like normal business communication.

Therefore, employees must focus less on grammar. Instead, they should focus on what the message asks them to do.

Watch the request, not just the writing

A polished email can still be dangerous. For example, a message may ask an employee to change banking information. Another may request a password reset or verification code.

Urgency is another warning sign. Attackers often want the employee to act before checking the request.

Therefore, slow down when money, credentials, or sensitive data are involved. A short verification step can stop a costly mistake.

Verify payment and banking changes another way

Business email compromise often targets accounting teams. An attacker may imitate a vendor or compromise a real mailbox.

The email may look completely normal. However, it may contain new payment instructions controlled by the attacker.

Always verify banking changes through a second channel. For example, call a known phone number already on file. Do not use the phone number included in the suspicious message.

Protect accounts with MFA

Multi-factor authentication adds another barrier after a password. Therefore, it can reduce the damage from stolen credentials.

However, MFA is not perfect. Attackers may still try to trick users into approving a login.

For that reason, employees should never approve an unexpected authentication request. In addition, businesses should use stronger authentication methods where practical.

Use email security and employee training together

Technology can block many malicious messages. However, no filter catches every scam.

Employees provide another layer of defense. Therefore, training should use realistic examples and simple verification rules.

Also, make reporting easy. Employees should know exactly where to send a suspicious message. A fast report can help IT protect other users before they click.

Build a simple verification culture

The best process does not depend on employees becoming security experts. Instead, give them clear rules.

For example, verify changes to payment information. Confirm unusual requests from executives. Never share a verification code by email or phone.

Graphene Technologies provides cybersecurity services for Houston businesses. We can help with email security, MFA, endpoint protection, monitoring, and user awareness. Schedule a free 30-minute IT assessment to identify your biggest security gaps.

Call to Action

Need a clearer picture of your IT risks and priorities? Schedule a Free 30-Minute IT Assessment with Graphene Technologies. We will review your current environment and identify practical next steps.

OneDrive versus SharePoint file storage comparison for Houston businesses using Microsoft 365

OneDrive vs. SharePoint: Where Houston Businesses Should Store Files

OneDrive and SharePoint solve different problems

OneDrive and SharePoint both store files in Microsoft 365. However, they are designed for different types of work.

OneDrive is primarily an individual’s workspace. SharePoint is designed for team and company information.

That difference matters because file ownership affects access and continuity. Therefore, choosing the right location can prevent problems when employees change roles or leave.

Use OneDrive for individual working files

OneDrive works well for documents that one employee owns while creating or editing them. For example, drafts and personal working notes often belong there.

In addition, OneDrive makes those files available across approved devices. Employees can also share a file when collaboration is temporary.

However, OneDrive should not become the permanent home for important department records. If the business depends on a file, move it to a team-owned location.

Use SharePoint for team and company information

SharePoint works better for files that belong to a department, project, or the company. Examples include procedures, templates, marketing assets, and shared operational documents.

Because SharePoint belongs to the organization, access does not depend on one employee’s account. As a result, the business keeps control when staffing changes.

SharePoint also supports structured permissions. Therefore, teams can provide access based on roles instead of sharing files one person at a time.

Avoid the most common storage mistake

A common mistake is storing critical company files inside one employee’s OneDrive. At first, the setup seems convenient. However, problems appear when that employee leaves.

The business may then need to recover ownership, repair links, and rebuild access. In addition, coworkers may not know which files are current.

Instead, move shared business information to SharePoint. Then, use OneDrive for personal work in progress.

Keep permissions simple

Permissions become difficult when businesses create too many exceptions. Therefore, use groups whenever possible.

For example, create access around departments or job roles. Then, add and remove employees from those groups as responsibilities change.

Also, review external sharing regularly. Old sharing links can remain active long after a project ends. A recurring review helps remove access that is no longer needed.

Plan the structure before moving everything

Do not move years of files into SharePoint without a plan. First, decide which information belongs to each team. Next, remove duplicates and outdated content.

Then, create a simple folder and site structure. Keep names clear because employees need to find information quickly.

Graphene Technologies provides Microsoft 365 consulting for Houston businesses. We can help with OneDrive, SharePoint, permissions, migrations, backup, and security. Schedule a free 30-minute IT assessment to review your Microsoft 365 environment.

Call to Action

Need a clearer picture of your IT risks and priorities? Schedule a Free 30-Minute IT Assessment with Graphene Technologies. We will review your current environment and identify practical next steps.