News

Cameras, Gates and Smart Devices: 7 Steps to Keep Connected Equipment Secure

Security cameras, automatic gates, door controllers, network printers and smart sensors make offices, schools and hotels easier to run. But every one of these devices is a small computer connected to your network. If it is set up carelessly, it can become the easiest way for someone to reach your files, watch your premises or switch off a system you depend on. Here are seven practical steps to keep connected devices working for you, not against you.

1. Know what is connected

Start with a simple list: every camera, recorder, gate or door controller, printer, access point and sensor, with its location, model and who looks after it. Many organisations discover forgotten devices this way, such as an old recorder or a test camera still plugged in. You cannot protect what you do not know about.

2. Change default passwords on day one

Many devices leave the factory with a standard username and password that are published in manuals online. Change them before the device goes into service, use a different strong password for each device or group of devices, and store them in a secure place that more than one trusted person can reach.

3. Keep devices on their own network segment

Cameras and automation controllers rarely need to talk to staff laptops or accounting systems. Placing them on a separate VLAN or network segment, with firewall rules that allow only the traffic they need, limits the damage if one device is compromised. It also stops heavy video traffic from slowing down everyday work.

4. Be careful with remote access

Viewing cameras or opening a gate from your phone is convenient, but opening ports on your router so a device can be reached from the internet is risky. Where remote access is needed, prefer a secure VPN or the manufacturer’s properly configured service, limit it to the people who really need it, and remove access when staff leave.

5. Update firmware regularly

Manufacturers release firmware updates to fix security weaknesses and bugs. Set a routine, for example every quarter, to check for updates on recorders, cameras, controllers and network equipment. Before updating anything that controls access, such as a gate or door, plan a time when a short interruption will not cause problems.

6. Protect power, storage and recordings

A camera system is only useful if the recorder is running and the footage is there when you need it. Use surge protection and, where it makes sense, a UPS for recorders and network switches. Decide how long recordings should be kept, check storage health, and make sure only authorised people can view or export footage.

7. Check and test, not just install

Once a month, take a few minutes to confirm that every camera is recording, the time and date are correct, gates and doors respond properly, and no unknown devices have appeared on the network. Keep a short log of what you checked and any changes made. Small, regular checks catch problems long before an incident does.

Bringing it together

Connected devices should make your premises safer and your operations smoother. With a clear inventory, strong passwords, a separated network, careful remote access and regular checks, they can do exactly that without opening new doors to risk.

Talk to eDruk

eDruk Private Limited has been working in software and ICT in Bhutan since 2004, including networking, IoT and automation, and technical consultation. If you would like help reviewing how your cameras, gates and other connected devices are set up, or planning a new installation, get in touch:

• Email: edruk@edruk.com.bt
• Phone: +975 2 332277
• Website: https://www.edruk.com.bt

News

After Go-Live: 7 Things to Plan for Software Maintenance and Support

Launching a new website, web application or mobile app is an exciting milestone. But go-live is not the finish line. From the day real users start relying on it, software needs steady care to stay secure, fast and useful. Organisations that plan for this early avoid surprise outages, security gaps and costly rebuilds a few years later.

Here are seven practical things to plan for after your software goes live.

1. Agree on who looks after it

Decide clearly who is responsible once the project is handed over: your in-house IT team, the original developer, or a support partner. Write down who receives problem reports, who can approve changes and how urgent issues are escalated. When everyone knows the process, small problems get fixed before they grow.

2. Keep software and dependencies updated

Most modern systems are built on frameworks, plugins, libraries and server software that receive regular updates, many of them security fixes. Schedule time to apply these updates, test them first where possible, and keep a record of what changed. Outdated components are one of the most common ways websites and applications get compromised.

3. Back up data and test restores

Your database, uploaded files and configuration are often more valuable than the code itself. Make sure backups run automatically, are stored in more than one place, and are tested by actually restoring them from time to time. A backup that has never been tested is only a hope.

4. Monitor uptime, performance and errors

Do not wait for customers or staff to tell you the system is down. Simple monitoring can alert you when a site stops responding, when pages become slow, or when errors start appearing in the logs. Watching disk space, SSL certificate expiry dates and domain renewals also prevents some very avoidable outages.

5. Review security and user access regularly

Staff change roles and leave, and accounts are often forgotten. Review administrator and user accounts every few months, remove those that are no longer needed, and enforce strong passwords or two-factor authentication where the system supports it. Check that sensitive data is only visible to the people who genuinely need it.

6. Listen to users and plan improvements

Real-world use always reveals things nobody expected during development: a confusing form, a missing report, a step that takes too long. Collect this feedback in one place, group it, and plan small improvements in regular cycles rather than waiting for a large and risky overhaul.

7. Keep documentation up to date

Good documentation covers how the system is hosted, where the source code lives, how to deploy updates, which accounts and services it depends on, and how to restore it after a failure. Keeping this current means your organisation is not dependent on one person’s memory, and it makes any future handover much smoother.

Plan maintenance from day one

The best time to think about maintenance is before launch, when you are setting the scope and budget for a project. Including updates, backups, monitoring and support in your plan from the start keeps your software reliable for years instead of months.

Talk to eDruk

eDruk Private Limited has been building and supporting software in Bhutan since 2004, including websites, web applications and mobile apps. If you would like help reviewing an existing system or planning maintenance and support for a new one, get in touch with our team.

Email: edruk@edruk.com.bt
Phone: +975 2 332277
Website: www.edruk.com.bt

News

Reliable Wi-Fi for Offices, Schools and Hotels: 7 Things to Plan for Full Coverage

Slow or patchy Wi-Fi is one of the most common complaints in offices, schools, hotels and homes. Very often the internet connection itself is fine. The real problem is how the wireless network inside the building was planned. Thick stone or concrete walls, several floors and a growing number of phones and laptops can quickly overwhelm a single router placed in a corner. Here are seven practical things to plan for reliable Wi-Fi coverage.

1. Start with how the space is used

Before choosing equipment, walk through the building and note where people actually work, meet and connect. A conference room, a classroom or a hotel lobby may have many devices at once, while a store room may need almost none. Planning around real usage helps you place coverage where it matters instead of spreading it evenly and hoping for the best.

2. Respect walls, floors and materials

Wireless signals weaken as they pass through walls and floors. Traditional buildings with thick masonry, concrete slabs, metal roofing or mirrored glass can block Wi-Fi far more than lighter partitions. A quick site survey to check signal strength room by room shows where extra access points are needed, so you avoid dead zones after installation.

3. Use several access points, not one powerful router

A single router turned up to full power rarely solves coverage problems. Several properly placed access points, usually mounted on ceilings or high on walls, give more even coverage and share the load between users. When they are managed as one network, devices can move between rooms without losing their connection.

4. Plan the wired backbone too

Good Wi-Fi depends on good cabling. Each access point should ideally connect back to a network switch with a proper structured cable, and switches that provide Power over Ethernet (PoE) can power access points through the same cable. Planning cable routes, a tidy network rack and spare capacity at the start makes later expansion much easier.

5. Separate staff, guest and device networks

Not every device should share the same network. A common approach is to keep staff computers on one network, give visitors or guests a separate network with internet-only access, and place devices such as printers, cameras or smart equipment on their own segment. This keeps important systems safer and makes problems easier to troubleshoot.

6. Secure it from day one

Use current encryption (WPA2 or WPA3), strong passwords that are changed when staff leave, and change the default admin login on every router and access point. Keep firmware up to date, and avoid sharing the main office password with visitors when a guest network can do the job.

7. Test, document and maintain

After installation, test coverage and speed in every important area, not just near the equipment. Keep a simple record of where each access point is, how the networks are set up and who manages them. Regular checks and firmware updates help the network stay reliable as more devices are added over time.

Need help planning your wireless network?

eDruk Private Limited has been working on software and ICT solutions in Bhutan since 2004, including networking and infrastructure. Whether you are setting up a new office, upgrading a school or hotel, or fixing persistent dead zones, our team can help you assess your site and plan a network that fits your needs.

Email: edruk@edruk.com.bt
Phone: +975 2 332277
Website: https://www.edruk.com.bt