EBUS > EBUS-Hidden Camera Computer Speakers #BBCompSPK

Protect your proprietary secrets by catching the spy in the act. On video.

• Completely covert design. Looks like a set of speakers, because it is a set of speakers.
• True VGA quality resolution.
• 30+ FPS.
• Auto electric shutter and white balance.
• RCA connection for video.

• 2.0" LCD TFT display.
• 640 x 480, 480 x 240, 160 x 120 @ 30FPS.
• Supports up to a 4GB mini SD card.
• 4GB Mini SD card, High resolution 14 hours, Low resolution ~45 hours.
• Recording format AVI, ASF, MOV.
• 45MB built in memory.
• 5V DC.

Button camera

• 0.3 LUX. (Luminous Emmitance) which is an incredibly small amount of distracting light created by this product.
• 420 lines of resolution (same as a television).
• One cable 3 ring, 2.5mm gold.
• Physical Measurements: 19X19 cm.

• DV950A digital video recorder.
• USB cord.
• Wall charger.
• AV In/Out cable
• BC420 button camera
• A/V plug.

Bigger isn't always better. Compact size can be critical, but it's useless without top-notch performance. Some little DVRs claim to be the world's smallest. Not only are they larger than this unit, they don't deliver nearly as good an image.

What you record onto this next-generation DVR you can play back on a full-sized screen with no loss of quality. This supports up to a 4 GB mini SD card for up to 14 hours of high-resolution video, more than three times as much at lower resolution. And you can easily tuck it away in a pocket.

Most DVRs on the market can record video at320X480 @15 FPS, one other model can do as much as 640X480 @ 15 to 18 FPS. Some claim that you can upgrade the firmware and get better resolution (that's simply not possible as resolution cannot increase without degradation of the image, it's like blowing a balloon with writing on it, sure you can make it bigger but past some point the image will degrade).

Resolution is the SIZE of the image of 640 pixels horizontal by 480 pixels vertical, which is perfect as these just happen to be your PC's VGA standards.

This is a favorite camera among private investigators, law enforcement, OGA and (Office of the General Assembly). This product has also been used with radio controlled toy cars and by ACTUAL professional car drivers.

• Don't announce you've installed a hidden camera. This may sound obvious, but it's a rule many people break.
• Keep the existence of the camera on a "need to know" basis. The fewer people who know, the better.
• If installing a camera in a bathroom or other normally private location (due to drug use, vandalism, etc.), consult an attorney about privacy violation issues first.
• Take a cue from Realtors. Location, location, location. It's critical you install the camera where it can be concealed, but also where its viewing field won't be inadvertently blocked by people standing in front of it. It also needs to be fairly accessible for such things as retreiving the flashdrive, recharging the battery, cleaning the lens, etc.
• Run a test once you've installed it. You may need to adjust angle, ambient lighting, height, focus, etc., to get the kind of footage you want.
• Develop a schedule for accessing it without revealing that it's there. Obviously, pulling the flashdrive out of the breakroom monitoring camera during lunchtime isn't going to work.

Home security. You may have heard the expression, "When seconds count, the cops are only minutes away." Cameras and other detection devices are great, but what's the execution plan? Don't think "detect and report," think "detect and protect." The most effective home protection device is a shotgun. Typically, it doesn't need to be fired to have the desired effect. But this isn't the only protection measure. You can also have an escape and assembly plan, a safe room, or some other measure. Yes, install those detection devices. But don't think that simply knowing your perimeter is breached makes you safe.

Corporate customers. Your situation is similar to that of the consumer, except there are more people involved and the property values are significantly greater. Also, consumers tend to be home at night and corporate customers are on the other shift so to speak. Corporate security specialists must also protect information, not just property or people. Not only do you need a perimeter breach detection system, but you need a high level of employee education on a wide range of security subjects. And this is where most corporate security bites the dust.

For example, consider usernames and passwords. Most employees think it's OK to give out one as long as you don't give out both. But there's a reason why you have both. And if you give out one, the other is probably easy to guess. Yes, you need to use technology wherever practical to counter theft and espionage, and to protect people from physical dangers. Don't stop there.

Put together a presentation on each security aspect (e.g., passswords would be one aspect; keycards another; suspicious persons another) and meet with all employees in a series of meetings consisting of small groups. The small group approach helps ensure people are fully participating. Absolutely do not use PowerPoint, which tends to render any attempt at actual communication a failed example of PowerPointlessness. Keep the meetings to about 10 minutes or less, so that people completely focus. Sure, this is not the typical meeting methodology, but then the typical meeting is a complete waste of time. Make your time count and get your message across.

Successful security planning. Fads come and go. We see it all the time. Manager who try launching a new program, often get that respons from employees. Anyone remember "Vision 2000?" The problem is that people see the plan as the end rather than a means to an end. So they polish the plan and forget why they are planning in the first place.

When plans roll out, they often seem absurd to the rank and file. And why is that? Because they are absurd! That is often true of security plans. These plans suffer from several different maladies. Sometimes all at once. These include the following.

• Overplanning. Never get started, because the plan isn't done.
• Underplanning. Going full bore, without a roadmap.
• Changing directions, midstream. This really confuses people. It happens because planners are still learning.
• Complexity. A simple plan, after all that work, seems like a letdown. The solution? Make things complicated. Add stuff that doesn't make sense. The more complex, the better, right? Wrong. Greater complexity just means more ways it can fail. Aim for simplicity.
• Covers too much. Can't leave anything to chance, right? Wrong. The more you try to cover, the more you dilute your resources. Focus on that which is most dangerous or costly. Let some things go, so you can do the job right on what matters.
• Apes someone else's plan. Just because it worked for someone else doesn't mean it will work for you. The idea of best practices is not copy and paste.
• It's top down. Your plan will fail if it assumes your people are the problem. Make them part of the solution. Form an advisory board that includes people from different parts of the company. You get insight from many angles, that way. And you have advocates for your plan at all levels, that way.

Rather than roll out some big plan, roll out a series of smaller ones. Make them modules for a larger plan. Module 1 might be bug detection. Buy a bug detector, and learn how to use it. Learn what to do about bugs. Fully develop that plan as you work through the module. Then you can apply the lessons you learned to the next module. Whatever that happens to be.

Once you've picked the low-hanging fruit, you can assess the need for calling in a security consultant. This person can evaluate your existing modules and suggest improvements. He or she can also suggest what module to develop next. And how best to go about it.

This approach allows you to get the highest return on your effort. And the fastest results. And good compliance.