Tag: Cloud Security

  • NIST Finalizes Guidance for Protecting Online Identity and Access Tokens

    NIST Finalizes Guidance for Protecting Online Identity and Access Tokens

    NIST has finalized implementation guidance for protecting online identity and access tokens from theft, forgery and misuse. Tokens allow applications and services to recognize authenticated users without repeatedly asking for credentials, but stolen or forged tokens can let an attacker impersonate a legitimate account while bypassing normal sign-in checks.

    The guidance uses a reference cloud implementation

    The publication describes a zero-trust architecture built around commercial and open-source technologies. It covers token discovery, visibility, validation and enforcement across identity providers, applications and cloud services. NIST developed the practice guide with CISA and industry collaborators through the National Cybersecurity Center of Excellence.

    The final material emphasizes that token protection is not limited to one product. Organizations need coordinated telemetry and policy enforcement across the systems that issue, receive and validate tokens.

    Operations should test revocation and misuse detection

    Identity teams should inventory token types, document trust relationships, reduce unnecessary token lifetime and confirm that revocation works during an incident. Monitoring should identify unusual issuance, replay and use from unexpected devices or locations. Those controls complement phishing-resistant authentication rather than replacing it. SectechMedia follows related developments in its identity and access-control coverage.

    Sources

  • Cloudflare Fixes Cross-Tenant Disk Data Exposure in Container Platform

    Cloudflare Fixes Cross-Tenant Disk Data Exposure in Container Platform

    Cloudflare has disclosed and fixed a cross-tenant data exposure issue affecting its Containers and Sandboxes products. The flaw involved storage reuse: a newly provisioned workload could receive disk blocks that still contained residual data from a previous customer.

    How the isolation failure occurred

    Researchers at Accomplish demonstrated that discarded thin-provisioned storage was not reliably cleared before reuse. That created a path for one tenant to inspect fragments left by another. Cloudflare said the affected products were in beta and reported no evidence that the issue had been exploited maliciously.

    The company disabled the relevant storage behavior, introduced sanitization controls and reviewed the platform after receiving the report. Cloudflare’s account and the researchers’ technical write-up agree on the core risk, although they describe some affected service details differently. The incident illustrates that workload isolation depends on storage lifecycle controls as well as compute and network boundaries.

    Lessons for multi-tenant platforms

    Operators should include block-device reuse, snapshot handling and deprovisioning in tenant-isolation tests. Encryption, secure erase procedures and monitoring for unexpected reads can add defense in depth, but each control must be verified against the actual storage architecture. Customers should also avoid treating beta isolation guarantees as equivalent to mature production assurance. Related coverage appears in SectechMedia’s cyber-physical security channel.

    Sources

  • Thales Launches UK-Hosted Luna Cloud HSM Service

    Thales Launches UK-Hosted Luna Cloud HSM Service

    Thales announced on September 14 a UK-hosted version of Luna Cloud HSM, its hardware-security-module capability delivered as a cloud service. The company says customer keys can be generated, stored, used, backed up and destroyed within UK-hosted infrastructure.

    Two UK instances are intended to support availability and disaster recovery within the country. The service is positioned for organizations that need to separate the location of application data from control of the cryptographic keys used to protect it.

    Claims about service architecture and compliance originate with Thales and should be treated as vendor statements unless checked against the relevant independent validation records and customer-specific configuration. UK hosting also does not remove the need for access governance, backup policy and key-lifecycle controls.

    Why it matters

    Data residency answers where data is stored; key sovereignty asks who can authorize decryption and under which jurisdiction. Regulated organizations increasingly need evidence for both questions when evaluating cloud security architecture.

    For wider context, see SectechMedia’s related technical coverage.

    Sources

  • Edge vs Cloud in Physical Security

    Edge vs Cloud in Physical Security

    Physical security now depends on where data is processed. Cameras can analyze video at the edge, on-site servers can run analytics, and cloud platforms can centralize management across many locations.

    What edge means

    Edge processing happens close to the sensor. A camera may classify people and vehicles locally, record to onboard storage and send only metadata or alarms, reducing bandwidth and preserving local operation.

    What cloud means

    Cloud platforms provide centralized management, remote access, scalable computing and software updates, particularly for distributed organizations that do not maintain servers at every site.

    Latency, bandwidth and resilience

    Local decisions can reduce latency for immediate actions. Systems must also define what happens during WAN failure: critical cameras should keep recording and doors should continue enforcing access rules.

    Cybersecurity and cost

    Cloud services centralize identity and updates but introduce vendor and account risks. Edge fleets require local patching. Cost comparisons should include servers, subscriptions, bandwidth, maintenance, replacement and staffing.

    Hybrid architecture

    Many organizations record locally while using cloud management and health monitoring. Basic analytics may run at the edge while cross-site search uses centralized services.

    Conclusion

    Edge is strong for autonomy and low latency; cloud is strong for scale and management. A deliberate hybrid design often provides the best balance.