Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Saturday, March 02, 2013

manfaat menjadi anggota Apkomindo


Bagi toko/perusahaan yang

 berorientasi pameran dan retail :

  • berkesempatan untuk mengikuti pameran yang diselenggarakan Apkomindo dan/atau mitra setahun 6 kali.
  • kesempatan untuk mengikuti product launching dan gathering dari para principal atau vendor nasional
  • kesempatan untuk mengikuti sales training dan workshop dari para principal atau vendor nasional
  • kemudahan untuk memperoleh produk dan keringanan tempo pembayaran dari para master dealer anggota apkomindo

Bagi toko/perusahaan yang berorientasi proyek pemerintah :

  • kemudahan untuk memperoleh surat dukungan dari master dealer atau distributor
  • informasi adanya lelang atau tender yang diselenggarakan pemerintah provinsi maupun pemerintah kabupaten/kota.
  • Saat ini Bappenas sedang mengusulkan (kembali) sertifikasi untuk asosiasi profesi sebagai syarat ikut lelang. Hanya asosiasi yang sudah mapan (established) yang berhak mengeluarkan sertifikat.

Manfaat secara umum bagi anggota asosiasi :

  • acara-acara gathering, olahraga, dan pertemuan berkala bagi anggota untuk mempererat hubungan antar anggota baik secara individu maupun perusahaan.
  • Tukar informasi dan komunikasi melalui mailing list, website, dan media komunikasi lainnya, baik mengenai organisasi, perkembangan TIK, harga produk, info produk, dlsb.
  • Kesempatan untuk memperoleh pelatihan, training, workshop, seminar dengan harga khusus, baik yang diselenggarakan oleh Asosiasi, Kadin, atau mitra.
  • Dukungan dari anggota maupun pengurus manakala terjadi musibah/duka cita maupun peristiwa sukacita.
  • Fasilitas untuk anggota yang memiliki kegemaran/hobi yang sama untuk menyalurkan hobinya, baik dengan fasilitasi asosiasi maupun swadaya, misalnya dalam kegiatan olahraga, seni (i.e fotografi, musik), dan kegemaran lainnya.
  • Kesempatan dan subsidi untuk anggota bilamana ada acara wisata domestik atau manca negara maupun acara ekstra organisasi lainnya.

Wednesday, February 27, 2013

BikeBox - geo-tag yang menarik

Created By: Sabine Gruffat & Bill Brown
BIKE BOX is a participatory locative media project and database created by Sabine Gruffat and Bill Brown. Using open-source software, participants will be able to listen to and contribute geotagged audio that relates or responds to specific locations in Brooklyn, New York: Williamsburg, Greenpoint, and along the waterfront. The audio can take any form, including (but not limited to) sound art, personal anecdotes, field recordings, radical histories, experimental music, or audio interviews.
BIKE BOX will be at Devotion Gallery in Brooklyn from July 16th – 25th, 2010. Three technology-enhanced bicycles available to the public will allow users to connect to the project database and hear sounds geocoded for specific locations in the target area. People with iPhones may also download the free BIKE BOX application at the gallery. An installation inside the gallery will allow visitors to listen to audio from the BIKE BOX database and to track the progress of BIKE BOX users in real time as they ramble and roll through Brooklyn.

Bike Box is a mobile-media bicycle library and interactive installation housed at Devotion Gallery, allowing participants to check out cheap, durable, technology-enhanced bikes and a free open source iPhone application developed for this installation.  As participants pedal around central Brooklyn, they are able to contribute site-specific audio through the iPhone application, as well as listen to a curated collection of geo-specific sounds provided by a variety of local land-use experts, historians, poets, artists, and other interpreters.  Bike Boxhopes to explore and give participants access to the layers of lived experience, personal anecdote, and history that are piled up invisibly on every street corner and city block.

Monday, February 25, 2013

11 Sumber Cloud Computing

26 Comments

SUMMARY:
Open-source software has been on the rise at many businesses during the extended economic downturn, and one of the areas where it is starting to offer companies a lot of flexibility and cost savings is in cloud computing. Cloud deployments can save money, free businesses from [...]
digg Open-source software has been on the rise at many businesses during the extended economic downturn, and one of the areas where it is starting to offer companies a lot of flexibility and cost savings is in cloud computing. Cloud deployments can save money, free businesses from vendor lock-ins that could really sting over time, and offer flexible ways to combine public and private applications. The following are 11 top open-source cloud applications, services, educational resources, support options, general items of interest, and more.
Eucalyptus. Ostatic broke the news about UC Santa Barbara’s open-source cloud project last year. Released as an open-source (under a FreeBSD-style license) infrastructure for cloud computing on clusters that duplicates the functionality of Amazon’s EC2, Eucalyptus directly uses the Amazon command-line tools. Startup Eucalyptus Systems was launched this year with venture funding, and the staff includes original architects from the Eucalyptus project. The company recently released its first major update to the software framework, which is also powering the cloud computing features in the new version of Ubuntu Linux.
Red Hat’s Cloud. Linux-focused open-source player Red Hat has been rapidly expanding its focus on cloud computing. At the end of July, Red Hat held its Open Source Cloud Computing Forum, which included a large number of presentations from movers and shakers focused on open-source cloud initiatives. You can find free webcasts for all the presentations here. The speakers include Rich Wolski (CTO of Eucalyptus Systems), Brian Stevens (CTO of Red Hat), and Mike Olson (CEO of Cloudera). Stevens’ webcast can bring you up to speed on Red Hat’s cloud strategy. Novell is also an open source-focused company that is increasingly focused on cloud computing, and you can read about its strategy here.
Traffic Server. Yahoo this week moved its open-source cloud computing initiatives up a notch with the donation of its Traffic Server product to the Apache Software Foundation. Traffic Server is used in-house at Yahoo to manage its own traffic, and it enables session management, authentication, configuration management, load balancing, and routing for entire cloud computing software stacks. Acting as an overlay to raw cloud computing services, Traffic Server allows IT administrators to allocate resources, including handling thousands of virtualized services concurrently.
Cloudera. The open-source Hadoop software framework is increasingly used in cloud computing deployments due to its flexibility with cluster-based, data-intensive queries and other tasks. It’s overseen by the Apache Software Foundation, and Yahoo has its own time-tested Hadoop distribution. Cloudera is a promising startup focused on providing commercial support for Hadoop. You can read much more about Cloudera here.
Puppet. Virtual servers are on the rise in cloud computing deployments, and Reductive Labs’ open-source software, built upon the legacy of the Cfengine system, is hugely respected by many system administrators for managing them. You can use it to manage large numbers of systems or virtual machines through automated routines, without having to do a lot of complex scripting.
Enomaly. The company’s Elastic Computing Platform (ECP) has its roots in widely used Enomalism open-source provisioning and management software,designed to take much of the complexity out of starting a cloud infrastructure. ECP is a programmable virtual cloud computing infrastructure for small, medium and large businesses, and you can read much more about it here.
Joyent. In January of this year, Joyent purchased Reasonably Smart, a fledgling open-source cloud startup based on JavaScript and Git. Joyent’s cloud hosting infrastructure and cloud management software incorporate many open-source tools for public and private clouds.  The company can also help you optimize a speedy implementation of the open-source MySQL database for cloud use.
Zoho. Many people use Zoho’s huge suite of free, online applications, which is competitive with Google Docs. What lots of folks don’t realize, though, is that Zoho’s core is completely open source — a shining example of how SaaS solutions can work in harmony with open source. You can find many details on how Zoho deploys open-source tools in this interview.
Globus Nimbus. This open-source toolkit allows businesses to turn clusters into Infrastructure-as-a-Service (IaaS) clouds. The Amazon EC2 interface is carried over, but is not the only interface you can choose.
Reservoir. This is the main European research initiative on virtualized infrastructures and cloud computing. It’s a far-reaching project targeted to develop open-source technology for cloud computing, and help businesses avoid vendor lock-in.
OpenNebula. The OpenNebula VM Manager is a core component of Reservoir. It’s an open-source answer to the many virtual machine management offerings from proprietary players, and interfaces easily with cloud infrastructure tools and services. “OpenNebula is an open-source virtual infrastructure engine that enables the dynamic deployment and re-placement of virtual machines on a pool of physical resources,” according to project leads.
It’s good to see open-source tools and resources competing in the cloud computing space. The end result should be more flexibility for organizations that want to customize their approaches. Open-source cloud offerings also have the potential to keep pricing for all competitive services on a level playing field.

Sunday, February 24, 2013

Panduan keamanan fisik untuk Data Center Anda

A Guide to Physical Security for Data Centers

 July 26, 2012 2 Comments »
A Guide to Physical Security for Data Centers
The aim of physical data center security is largely the same worldwide, barring any local regulatory restrictions: that is, to keep out the people you don’t want in your building, and if they do make it in, then identify them as soon as possible (ideally also keeping them contained to a section of the building). The old adage of network security specialists, that “security is like an onion” (it makes you cry!) because you need to have it in layers built up from the area you’re trying to protect, applies just as much for the physical security of a data center.
There are plenty of resources to guide you through the process of designing a highly secure data center that will focus on building a “gold standard” facility capable of hosting the most sensitive government data. For the majority of companies, however, this approach will be overkill and will end up costing millions to implement.
When looking at physical security for a new or existing data center, you first need to perform a basic risk assessment of the data and equipment that the facility will hold according to the usual impact-versus-likelihood scale (i.e., the impact of a breach of the data center versus the likelihood of that breach actually happening). This assessment should then serve as the basis of how far you go with the physical security. It is impossible to counter all potential threats you could face, and this is where identification of a breach, then containment, comes in. By the same token, you need to ask yourself if you are likely to face someone trying to blast their way in through the walls with explosives!
There are a few basic principles that I feel any data center build should follow, however:
  • Low-key appearance: Especially in a populated area, you don’t want to be advertising to everyone that you are running a data center. Avoid any signage that references “data center” and try to keep the exterior of the building as nondescript as possible so that it blends in with the other premises in the area.
  • Avoid windows: There shouldn’t be windows directly onto the data floor, and any glazing required should open onto common areas and offices. Use laminate glass where possible, but otherwise make sure windows are double-glazed and shatter resistant.
  • Limit entry points: Access to the building needs to be controlled. Having a single point of entry for visitors and contacts along with a loading bay for deliveries allows you to funnel all visitors through one location where they can be identified. Loading-bay access should be controlled from security or reception, ideally with the shutter motors completely powered down (so they can’t be opened manually either). Your security personnel should only open the doors when a pre-notified delivery is arriving (i.e., one where security has been informed of the time/date and the delivery is correctly labelled with any internal references). Of course all loading-bay activity should also be monitored by CCTV.
  • Anti-passback and man-traps: Tailgating (following someone through a door before it closes) is one of the main ways that an unauthorized visitor will gain access to your facility. By implementing man-traps that only allow one person through at a time, you force visitors to be identified before allowing access. And anti-passback means that if someone tailgates into a building, it’s much harder for them to leave.
  • Hinges on the inside: A common mistake when repurposing an older building is upgrading the locks on doors and windows but leaving the hinges on the outside of the building. This makes is really easy for someone to pop the pins out and just take the door off its hinges (negating the effect of that expensive lock you put on it!).
  • Plenty of cameras: CCTV cameras are a good deterrent for an opportunist and cover one of the main principles of security, which is identification (both of a security breach occurring and the perpetrator). At a minimum you should have full pan, tilt and zoom cameras on the perimeter of your building, along with fixed CCTV cameras covering building and data floor entrances/exits. All footage should be stored digitally and archived offsite, ideally in real time, so that you have a copy if the DVR is taken during a breach.
  • Make fire doors exit only (and install alarms on them): Fire doors are a requirement for health and safety, but you should make sure they only open outward and have active alarms at all times. Alarms need to sound if fire doors are opened at any time and should indicate, via the alarm panel, which door has been opened; it could just be someone going out for a cigarette, but it could also be someone trying to make a quick escape or loading up a van! On the subject of alarms, all doors need to have  alarms and be set to go off if they are left open for too long, and your system should be linked to your local police force, who can respond when certain conditions are met.
  • Door control: You need granular control over which visitors can access certain parts of your facility. The easiest way to do this is through proximity access card readers (lately, biometrics have become more common) on the doors; these readers should trigger a maglock to open. This way you can specify through the access control software which doors can be opened by any individual card. It also provides an auditable log of visitors trying to access those doors (ideally tied in with CCTV footage), and by using maglocks, there are no tumblers to lock pick, or numerical keypads to copy.
  • Parking lot entry control: Access to the facility compound, usually a parking lot, needs to be strictly controlled either with gated entry that can be opened remotely by your reception/security once the driver has been identified, or with retractable bollards. The idea of this measure is to not only prevent unauthorized visitors from just driving into your parking lot and having a look around, but also to prevent anyone from coming straight into the lot with the intention of ramming the building for access. You can also make effective use of landscaping to assist with security by having your building set back from the road, and by using a winding route into the parking lot, you can limit the speed of any vehicles. And large boulders make effective barriers while also looking nice!
  • Permanent security staff: Many facilities are manned with contract staff from a security company. These personnel are suitable for the majority of situations, but if you have particularly sensitive data or equipment, you will want to consider hiring your security staff permanently. A plus and minus of contract staff is that they can be changed on short notice (e.g., illness is the main cause of this). But it creates the opportunity for someone to impersonate your contracted security to gain access. You are also at more risk by having a security guard who doesn’t know your site and probably isn’t familiar with your processes.
  • Test, test and test again: No matter how simple or complex your security system, it will be useless if you don’t test it regularly (both systems and staff) to make sure it works as expected. You need to make sure alarms are working, CCTV cameras are functioning, door controls work, staff understands how visitors are identified and, most importantly, no one has access privileges that they shouldn’t have. It is common for a disgruntled employee who has been fired to still have access to a building, or for a visitor to leave with a proximity access card that is never canceled; you need to make sure your HR and security policies cover removing access as soon as possible. It’s only by regular testing and auditing of your security systems that any gaps will be identified before someone can take advantage of them.
  • Don’t forget the layers: Last, all security systems should be layered on each other. This ensures that anyone trying to access your “core” (in most cases the data floor) has passed through multiple checks and controls; the idea is that if one check fails, the next will work.
The general rule is that anyone entering the most secure part of the data center will have been authenticated at least four times:
1. At the outer door or parking entrance. Don’t forget you’ll need a way for visitors to contact the front desk.
2. At the inner door that separates the visitors from the general building staff. This will be where identification or biometrics are checked to issue a proximity card for building access.
3. At the entrance to the data floor. Usually, this is the layer that has the strongest “positive control,” meaning no tailgating is allowed through this check. Access should only be through a proximity access card and all access should be monitored by CCTV. So this will generally be one of the following:
  • A floor-to-ceiling turnstile. If someone tries to sneak in behind an authorized visitor, the door gently revolves in the reverse direction. (In case of a fire, the walls of the turnstile flatten to allow quick egress.)
  • A man-trap. Provides alternate access for equipment and for persons with disabilities. This consists of two separate doors with an airlock in between. Only one door can be opened at a time and authentication is needed for both doors.
4. At the door to an individual server cabinet. Racks should have lockable front and rear doors that use a three-digit combination lock as a minimum. This is a final check, once someone has access to the data floor, to ensure they only access authorized equipment.
The above isn’t an exhaustive list but should cover the basics of what you need to consider when building or retrofitting a data center. It’s also a useful checklist for auditing your colocation provider if you don’t run your own facility.
In the end, however, all physical security comes down to managing risks, along with the balance of “CIA” (confidentiality, integrity and access). It’s easy to create a highly secure building that is very confidential and has very high integrity of information stored within: you just encase the whole thing in a yard of concrete once it’s built! But this defeats the purpose of access, so you need a balance between the three to ensure that reasonable risks are mitigated and to work within your budget—everything comes down to how much money you have to spend.
About the Author
David Barker is technical director of 4D Data Centres. David (26) founded the company in 1999 at age 14. Since then he has masterminded 4D’s development into the full-fledged colocation and connectivity provider that it is today. As technical director, David is responsible for the ongoing strategic overview of 4D Data Centres’ IT and physical infrastructure. Working closely with the head of IT server administration and head of network infrastructure, David also leads any major technical change-management projects that the company undertakes.
Photo courtesy of S@veOurSm:)e