We’re Tracking the Future of Security

Tag: Network Security

  • PoE Power Budgeting for Security Cameras and Access Control

    PoE Power Budgeting for Security Cameras and Access Control

    Power over Ethernet simplifies security installations by carrying data and electrical power over the same structured cabling. Simplicity at the endpoint can hide a system-level constraint: the switch or injector still has a finite power budget, and the connected load changes with heaters, infrared illumination, motors and door hardware.

    Start With the Powered Device

    Use the manufacturer’s declared power class and maximum consumption for each camera, reader, intercom or controller. A camera that draws modest power in daylight may require more when infrared LEDs, a heater, a wiper or pan-tilt-zoom motors operate. Design against the credible maximum operating state, not the average shown on a quiet bench.

    Separate Port Capacity From Total Budget

    A switch can support a particular power level on an individual port while lacking enough total capacity to deliver that level on every port simultaneously. Add the endpoint requirements, reserve capacity for startup and future change, and check the power supply actually fitted to the switch. Modular switches may have different budgets depending on installed supplies.

    Cabling and Distance

    Voltage loss rises with cable resistance. Use compliant cabling, connectors and installation practice, especially for long outdoor runs or bundles exposed to heat. Extenders and intermediate devices add their own consumption and failure points. For distant perimeter equipment, local fiber plus a properly protected remote power source may be more resilient than stretching copper beyond its intended design.

    Backup Power Changes the Calculation

    If the security network must operate during a mains failure, the UPS has to support both network electronics and the PoE load. Runtime calculations should include worst-case device demand and conversion losses. Load-shedding priorities can preserve critical entrances and cameras while disabling lower-priority devices.

    Commissioning Tests

    • Verify negotiated power class and actual draw at each port.
    • Force night mode, heaters and moving mechanisms where practical.
    • Test restart behavior after a complete power interruption.
    • Confirm UPS runtime with the operational PoE load.
    • Set monitoring alerts for overload, port denial and supply failure.

    Conclusion

    PoE reliability depends on more than selecting a switch with enough ports. A defensible design matches endpoint maxima, total supply capacity, cable conditions and backup-power objectives so security devices remain available during the operating states that create the greatest demand.

    Reference sources

  • Time Synchronization in Physical Security Systems: Why NTP Matters

    Time Synchronization in Physical Security Systems: Why NTP Matters

    A camera records motion at 14:03, an access-control panel logs a door opening at 14:01, and an intrusion sensor reports an alarm at 14:05. If those clocks are drifting, investigators cannot reliably determine whether the events belong to one incident. Time synchronization is therefore a security control, not a cosmetic system setting.

    Why a Common Clock Matters

    Video, access, intrusion, intercom and building systems create separate event streams. A common time source allows a management platform to reconstruct sequence, correlate alarms and support an audit trail. NIST guidance on log management treats consistent timestamps as part of useful event records, while NTP is the widely deployed protocol for synchronizing networked clocks.

    Designing the Time Architecture

    Define approved time sources, then make intermediate servers or controllers distribute time to field devices. Avoid letting every camera or panel reach arbitrary internet servers. Critical sites may use redundant internal sources backed by a trusted external reference. Network rules should allow only the required protocol paths.

    Time Zones and Daylight Saving

    Store or correlate events in a stable reference such as UTC, while displaying local time to operators. Document how daylight-saving changes are handled. Otherwise, repeated or skipped local times can make exported evidence ambiguous.

    Drift and Failure Monitoring

    Synchronization can fail silently because of blocked traffic, configuration errors, expired credentials or a device reset. Monitor offset, source reachability and last successful synchronization. An alarm threshold should reflect the investigative needs of the site rather than an arbitrary universal value.

    Security Considerations

    A false time source can disrupt logs and certificate checks. Use authenticated mechanisms where supported, restrict management access and protect the authoritative servers. Record configuration changes so an investigator can establish whether a clock was trustworthy during an incident.

    Operational Checklist

    • Maintain an inventory of devices and their configured source.
    • Use redundant, monitored time servers for critical systems.
    • Test exported video and access reports for consistent timestamps.
    • Document UTC, local-time and daylight-saving behavior.
    • Include clock health in commissioning and maintenance.

    Conclusion

    Time synchronization turns isolated records into a defensible event sequence. Treating NTP architecture, clock monitoring and timezone handling as part of commissioning prevents avoidable uncertainty when operators and investigators need the record most.

    Reference sources

  • Apple Releases iOS 27 and macOS 27 Security Updates Covering 200 Flaws

    Apple Releases iOS 27 and macOS 27 Security Updates Covering 200 Flaws

    Apple has published security notes for iOS 27, iPadOS 27 and macOS Golden Gate 27, documenting fixes across the kernel, WebKit and multiple system components. SecurityWeek’s review counted roughly 200 vulnerability entries across the releases.

    The issues span memory corruption, privilege escalation, information exposure and application or system termination. Counts across Apple bulletins can overlap because a vulnerability may affect more than one platform, so the figure should be read as the scale of the release set rather than 200 wholly separate attack paths on every device.

    Apple’s security-release page is the authoritative place to check which operating-system version addresses a specific CVE. Administrators should use that device-specific information instead of assuming every fix applies identically to all supported hardware.

    Why it matters

    Large coordinated update sets create an asset-management problem as much as a patching problem. Security teams need accurate device inventories, supported-version visibility and staged deployment plans that reduce exposure without interrupting critical mobile workflows.

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

    Sources

  • Researchers Detail Fortinet-Based Intrusion at Thai Broadband Provider

    Researchers Detail Fortinet-Based Intrusion at Thai Broadband Provider

    Threat-intelligence researchers at Hunt.io have documented an intrusion affecting a Thai broadband provider in which attackers targeted a FortiGate SSL VPN and later deployed the MeshCentral remote-management platform. SecurityWeek independently summarized the research on September 15.

    The observed infrastructure hosted reconnaissance scripts, vulnerability probes, brute-force utilities and privilege-escalation tools. Hunt.io’s account links the activity to exploitation of a Fortinet flaw, but attribution to a named threat group was not established in the public reporting.

    Remote-management software can have legitimate administrative uses, which makes context essential. In this case, its placement alongside offensive tooling and the intrusion path made it part of the incident evidence rather than proof that the software itself was malicious.

    Why it matters

    Broadband providers sit at the intersection of public communications and critical infrastructure. Internet-facing security appliances require rapid patching, while remote-administration activity needs monitoring that can distinguish expected maintenance from unauthorized persistence.

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

    Sources

  • Cyber-Physical Security Convergence: Why IT and Security Teams Are Merging

    Cyber-Physical Security Convergence: Why IT and Security Teams Are Merging

    Physical security systems increasingly run on IP networks, cloud services and software platforms, while cyber incidents can create physical consequences. This is pushing IT, cybersecurity and physical-security teams toward closer operational convergence.

    Physical devices are cyber assets

    Cameras, door controllers, intercoms, alarm panels and sensors contain processors, firmware and network interfaces. Weak credentials, vulnerable software or unnecessary services can turn protective equipment into a cyber entry point.

    Identity and incident convergence

    Joiner, mover and leaver processes should update both digital and physical permissions. Badge activity, login records, forced doors and camera status can also provide stronger incident context when correlated.

    Architecture and governance

    Security devices should not sit on unmanaged flat networks. Segmentation, secure remote access, logging and vulnerability management require shared ownership across IT, cyber and physical-security functions.

    Cloud and operational technology

    Vendor security posture becomes part of procurement as video and access platforms move to cloud services. Critical infrastructure must also consider OT systems that control physical processes.

    Benefits and limitations

    Convergence can improve asset visibility, investigation and policy consistency, but it does not require every department to merge. Clear responsibilities and escalation paths remain essential.

    Conclusion

    Unified identity, shared data and careful correlation will continue to drive cyber-physical convergence. Isolated facilities systems are increasingly difficult to govern securely.