William
I need to hook up an outdoor security camera system but one that is also wireless. I would need to view it on my ipad as I am going away on vacation so something that doesnt need recharging would be the best
Answer
Hello
Here is a DVR that will work perfectly for you.
http://www.ascendentgroup.com/x4s.htm
Most DVR's and cameras don't have the ability to view from your i-phone, and you cant just download generic software all DVR's and cameras uses different encryption , software, and compression so you cant use another companies software to view another manufactures DVR.
You want a DVR that has an app specifically designed to work with it like the one I am suggesting below.
What you want is a DVR a DVR converts analog cameras and as well as storing images on site allows you to distribute video over LAN and WAN networks. (internet and network) this way you have both on site storage and recording at your house.
A good Analog DVR will do what you are looking for and not only display them but record them as well they will also allow you to view them over the internet from a Iphone or laptop.
X4S Remote Accessibility
View all your cameras instantly and remotely, and configure the DVR through internet using eitherbusiness in real time from anywhere in the world. MAC or PC platforms (smart phones too). This allows you to manage your
Many people have a misconception that IP has Superior scalability then Analog but with the advancements with DVR's this simply isn't true, you cn do up to 16,000 cameras each camera could even be from a different DVR and a different site.
And when you are using the internet to connect multiple sites together analog transmits over the internet faster with less latency using less bandwidth allowing you not only to view and monitor a situation real time but also effective control PTZ cameras.
What is the Advantage of IP?
Many of the so called advantages of IP simply don't hold water in the real world, IP is mainly Hype and marketing and outside of a few niche applications such as 1 or 2 camera installs, where MP cameras are needed or large scale wireless projects which represent about 2% of the total CCTV market, IP has very few advantages compared to analog based on performance, cost and reliability. (yet all companies touting IP will often use MP cameras to demonstrate the advantages of IP)
IP video is more about marketing then it is about performance as larger companies like Bosch pelco Honeywell axis can change for both hardware and software and once you use there cameras you have to keep using there cameras unlike analog.
Also IP sounds great, plug and play, Better image quality, use existing infrastructure, who wouldnât want that unfortunately this is often not the case.
IP cameras are based on CMOS
Analog cameras are based on CCD (usually)
A CMOS sensor is constructed using a array of pixels, but unlike CCDâs CMOS do not have a capacitor to store the charge for each pixel.The rows of pixels are activated sequentially rather then individually
In short unless you have perfect lighting a good CCD camera will outperform an equivalent CMOS camera.
File Size:
The smaller the files size the more images that are able to be sent and the faster they can be processed improving both FPS and speed. File size is the heart of any DVR and goes far beyond just its streaming capabilities as it also determines the recoding storage time, how much you can back up at once, how fast it renders and searches video.
IP cameras have up to a 5X larger file size then analog cameras. (at same resolution) I have seen MP cameras that on 2MP resolution are over 300X (%3000) larger then our X3 DVR on a CIF image. This is an extreme case but generally speaking IP cameras have a much larger file size.
Most routers and switches are not designed to handle IP cameras they have enough bandwidth but they are not able to process the amounts of commands. (9 IP cameras 30FP is 230 instructions per second) standard routers have enough bandwidth (up to 1GB) but cant handle the amount of tasks (instructions) so frames get dropped latency is introduced and the effectiveness of other devices such as POS, printers and dats storage can be affected and compromised.
Donât get me wrong there are some brutal analog cameras and DVR out there but If you see a good D1 resolution image such as Ascendents Hardware compressed you will not be so quick to join the IP bandwagon.
IP is a young and emerging technology and I have no doubt that in the future it will outperform analog cameras but its not a mature technology yet. Once we start to get standard IP platforms, get rid of license feesâ and existing networks have larger bandwidths then IP video will be a good solution, but until then analog is the way to go.
Make sure you get good cameras as well, Ascendent has the best IR outdoor cameras on the market and are about %50 less then Bosch while offering triple the distance.
http://www.ascendentgroup.com/
Hello
Here is a DVR that will work perfectly for you.
http://www.ascendentgroup.com/x4s.htm
Most DVR's and cameras don't have the ability to view from your i-phone, and you cant just download generic software all DVR's and cameras uses different encryption , software, and compression so you cant use another companies software to view another manufactures DVR.
You want a DVR that has an app specifically designed to work with it like the one I am suggesting below.
What you want is a DVR a DVR converts analog cameras and as well as storing images on site allows you to distribute video over LAN and WAN networks. (internet and network) this way you have both on site storage and recording at your house.
A good Analog DVR will do what you are looking for and not only display them but record them as well they will also allow you to view them over the internet from a Iphone or laptop.
X4S Remote Accessibility
View all your cameras instantly and remotely, and configure the DVR through internet using eitherbusiness in real time from anywhere in the world. MAC or PC platforms (smart phones too). This allows you to manage your
Many people have a misconception that IP has Superior scalability then Analog but with the advancements with DVR's this simply isn't true, you cn do up to 16,000 cameras each camera could even be from a different DVR and a different site.
And when you are using the internet to connect multiple sites together analog transmits over the internet faster with less latency using less bandwidth allowing you not only to view and monitor a situation real time but also effective control PTZ cameras.
What is the Advantage of IP?
Many of the so called advantages of IP simply don't hold water in the real world, IP is mainly Hype and marketing and outside of a few niche applications such as 1 or 2 camera installs, where MP cameras are needed or large scale wireless projects which represent about 2% of the total CCTV market, IP has very few advantages compared to analog based on performance, cost and reliability. (yet all companies touting IP will often use MP cameras to demonstrate the advantages of IP)
IP video is more about marketing then it is about performance as larger companies like Bosch pelco Honeywell axis can change for both hardware and software and once you use there cameras you have to keep using there cameras unlike analog.
Also IP sounds great, plug and play, Better image quality, use existing infrastructure, who wouldnât want that unfortunately this is often not the case.
IP cameras are based on CMOS
Analog cameras are based on CCD (usually)
A CMOS sensor is constructed using a array of pixels, but unlike CCDâs CMOS do not have a capacitor to store the charge for each pixel.The rows of pixels are activated sequentially rather then individually
In short unless you have perfect lighting a good CCD camera will outperform an equivalent CMOS camera.
File Size:
The smaller the files size the more images that are able to be sent and the faster they can be processed improving both FPS and speed. File size is the heart of any DVR and goes far beyond just its streaming capabilities as it also determines the recoding storage time, how much you can back up at once, how fast it renders and searches video.
IP cameras have up to a 5X larger file size then analog cameras. (at same resolution) I have seen MP cameras that on 2MP resolution are over 300X (%3000) larger then our X3 DVR on a CIF image. This is an extreme case but generally speaking IP cameras have a much larger file size.
Most routers and switches are not designed to handle IP cameras they have enough bandwidth but they are not able to process the amounts of commands. (9 IP cameras 30FP is 230 instructions per second) standard routers have enough bandwidth (up to 1GB) but cant handle the amount of tasks (instructions) so frames get dropped latency is introduced and the effectiveness of other devices such as POS, printers and dats storage can be affected and compromised.
Donât get me wrong there are some brutal analog cameras and DVR out there but If you see a good D1 resolution image such as Ascendents Hardware compressed you will not be so quick to join the IP bandwagon.
IP is a young and emerging technology and I have no doubt that in the future it will outperform analog cameras but its not a mature technology yet. Once we start to get standard IP platforms, get rid of license feesâ and existing networks have larger bandwidths then IP video will be a good solution, but until then analog is the way to go.
Make sure you get good cameras as well, Ascendent has the best IR outdoor cameras on the market and are about %50 less then Bosch while offering triple the distance.
http://www.ascendentgroup.com/
how do you handle system security?
mukky
computer virus threats! how do you handle system security?
Answer
I've been taught to use layers of security, or "defense in depth".
Most of these practices & policies will be done over and over again - not a one-time fix, but a process.
At the lowest level, (your machine) - evaluate and address physical security. Do you need to keep this in a locked room so nobody tampers with it? Evaluate & update BIOS and Firmware if appropriate. Remove or block USB, CD/DVD and other drives if necessary.
Next level, the operating system: no matter what you use (Linux, Win, mac, others) make sure you limit administrator or root access and make strong passwords for all users.
(For Windows this means 15+ characters), Patch the OS on a regular schedule, and make sure to disable or remove any services or programs that aren't needed.
If this is a critical system, then some system-file checking system should be used. Make sure that system files haven't changed unless you change them. Update your information regularly, and keep the tables or checksums that you collect from that machine in a safe place (your only copy should not be on the same machine).
Turn on logging, and if practical - store the logs on another machine where they can't be easily tampered with.
Next level, applications: only install what you need, and clean up anything you remove. Manually verify that patches are done on a systematic schedule. Check for security 'best practices' - stuff like "chroot"-ing an Apache install, and input-verification on SQL-like databases. Again, if practical, log events and check file checksums.
Limit user access to application on a need-to-have basis.
Next level, loss prevention: Here's where your firewall, anti virus, anti-malware and user policies come in. Keep all users (even your admins) to the least privileges to get a job done. Have a system to add new users and remove old ones. Keep AV & other security apps patched, and make sure it is working.
If your users will comply, then training is a good thing. Explain why they can't use myspace / utorrent / aim on critical work machines, and hold them accountable if they do violate policy.
(* as Scheiner says, I think it was something like this.. users will try to step across policy bounds, and if your policy isn't enforced, word gets out fast. A poorly enforced policy is useless. Don't waste time making them.)
Review your firewall policy on some schedule, so you can tell if changes were made without authorization.
Review policies on a set schedule - everything from changing keys to the server room, changing passwords, who has night/ weekend access, whether devices like CDs and USB can be booted from or 'autoplay'-able.
Use a UPS (power supply) and keep the machines off the ground where water, bugs, or clumsy employees can damage them.
Write this stuff down as a policy, and be prepared to justify it to outsiders if you keep anybody else's data.
Next level: recovery planning
Frequent backups, of course.
Check those backups .. verify that you actually have a working backup, and check them for viruses. If practical, keep backups off-site. If you can technically perform and/or afford clustering, virtualization, or other fail-over solutions, then split your work up over 2 or more machines. If one fails, be ready to move to the backup. Lots of ways to do this in hardware or software.. one hardware package I recently read about was Novell's (just bought) "PlateSpin".
Put in some system so you (or appropriate people) get some kind of auto-message from your UPS if power fails, or get called if your network goes down. Your recovery plan needs a start point - usually something other than " Monday AM, the CEO calls and complains". Try to avoid that one :)
Depending on how critical your systems are, you may want to have 24/365 monitoring including video camera or recorded logs of swipe/key access to the server rooms.
Network security is a whole 'nuther animal.
Again, layers of security..
block ports you don't need, firewall users/ IPs you don't need, use a VPN if you can, change default passwords on routers & switches, restrict physical and virtual access.. etc.
I've been taught to use layers of security, or "defense in depth".
Most of these practices & policies will be done over and over again - not a one-time fix, but a process.
At the lowest level, (your machine) - evaluate and address physical security. Do you need to keep this in a locked room so nobody tampers with it? Evaluate & update BIOS and Firmware if appropriate. Remove or block USB, CD/DVD and other drives if necessary.
Next level, the operating system: no matter what you use (Linux, Win, mac, others) make sure you limit administrator or root access and make strong passwords for all users.
(For Windows this means 15+ characters), Patch the OS on a regular schedule, and make sure to disable or remove any services or programs that aren't needed.
If this is a critical system, then some system-file checking system should be used. Make sure that system files haven't changed unless you change them. Update your information regularly, and keep the tables or checksums that you collect from that machine in a safe place (your only copy should not be on the same machine).
Turn on logging, and if practical - store the logs on another machine where they can't be easily tampered with.
Next level, applications: only install what you need, and clean up anything you remove. Manually verify that patches are done on a systematic schedule. Check for security 'best practices' - stuff like "chroot"-ing an Apache install, and input-verification on SQL-like databases. Again, if practical, log events and check file checksums.
Limit user access to application on a need-to-have basis.
Next level, loss prevention: Here's where your firewall, anti virus, anti-malware and user policies come in. Keep all users (even your admins) to the least privileges to get a job done. Have a system to add new users and remove old ones. Keep AV & other security apps patched, and make sure it is working.
If your users will comply, then training is a good thing. Explain why they can't use myspace / utorrent / aim on critical work machines, and hold them accountable if they do violate policy.
(* as Scheiner says, I think it was something like this.. users will try to step across policy bounds, and if your policy isn't enforced, word gets out fast. A poorly enforced policy is useless. Don't waste time making them.)
Review your firewall policy on some schedule, so you can tell if changes were made without authorization.
Review policies on a set schedule - everything from changing keys to the server room, changing passwords, who has night/ weekend access, whether devices like CDs and USB can be booted from or 'autoplay'-able.
Use a UPS (power supply) and keep the machines off the ground where water, bugs, or clumsy employees can damage them.
Write this stuff down as a policy, and be prepared to justify it to outsiders if you keep anybody else's data.
Next level: recovery planning
Frequent backups, of course.
Check those backups .. verify that you actually have a working backup, and check them for viruses. If practical, keep backups off-site. If you can technically perform and/or afford clustering, virtualization, or other fail-over solutions, then split your work up over 2 or more machines. If one fails, be ready to move to the backup. Lots of ways to do this in hardware or software.. one hardware package I recently read about was Novell's (just bought) "PlateSpin".
Put in some system so you (or appropriate people) get some kind of auto-message from your UPS if power fails, or get called if your network goes down. Your recovery plan needs a start point - usually something other than " Monday AM, the CEO calls and complains". Try to avoid that one :)
Depending on how critical your systems are, you may want to have 24/365 monitoring including video camera or recorded logs of swipe/key access to the server rooms.
Network security is a whole 'nuther animal.
Again, layers of security..
block ports you don't need, firewall users/ IPs you don't need, use a VPN if you can, change default passwords on routers & switches, restrict physical and virtual access.. etc.
Powered by Yahoo! Answers
Tidak ada komentar:
Posting Komentar