|Product Name||General Services Administration Manual|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0808021559|
|Price New||288.96 US Dollars (curriencies)|
|Width||2 inches (convert)|
|Height||9 inches (convert)|
|Length||6 inches (convert)|
|Weight||28 ounces (convert)|
|Long Description||This edition includes the complete text of the GSAR (48 CFR 500-599) and related agency guidance. It also incorporates all GSAM changes issued through May 6, 2009 including complete rewrites for GSAR parts 509, 525, 528, 533, 537, 542, 543 and 549! Also included are important changes concerning bonds and insurance; contractor qualifications; application of labor laws to government acquisitions; protests, disputes and appeals; contract administration and audit services; termination of contracts, acquisitions of security and law enforcement by state and local governments through federal supply schedules, plus much more. The GSAM incorporates the General Services Administration Acquisition Regulation (GSAR) as well as internal agency acquisition policy. As a special feature of this book, we follow the GSAM format by having the GSAR material shaded. The shading helps users to distinguish and identify those parts that are regulatory from those that apply internally to GSA . The shaded parts are those subject to section 22 of the Office Federal Procurement Policy Act , as amended (41 U.S.C. 418b). GSA must publish these rules in the Federal Register and codify them in 48 CFR Chapter 5 in accordance with the Paperwork Reduction Act (44 U.S.C. 3051 et seq.) and the Regulatory Flexibility Act (5 U.S.C. 601 et seq.). The rules that require publication fall into two major categories: (1) Those that affect GSA ’s business partners (e.g., prospective offerors, contractors). (2) Those that apply to acquisition of leasehold interests in real property. The Federal Acquisition Regulation (FAR) does not apply to leasing actions, so the GSA establishes regulations for lease of real property under the authority of 40 U.S.C. 490 note. Separating regulatory material from internal directives decreases the number of rules subject to publication in the Federal Register. It also provides greater flexibility and responsiveness because an internal directive is easier and quicker to update or change.|
|Search Google||by EAN or by Title|
Article of interest
We are not hosted at GoDaddy, but we are registered there and have our DSN settings stored with them. So when Anonymous attacked GoDaddy, we were impacted too.
It is very sad that hackers don't think about all of the people that will be impacted by their actions. Even though we were not attacked directly, we were impacted and most of our users were also impacted.
Our site was up and running the entire time and because many DNS servers cache the address to our site, we had a steady flow of traffic during the attack. But the number of visiters to the site was clearly lower than normal. We had a significant drop in visitors and even after things were fixed by GoDaddy things weren't quite normal again until quite late in the evening.
If you or your applications were impacted by this attack we are deeply sorry but there was nothing that we could do to prevent or recover from this. Just like you, all we could do is wait for GoDaddy to deal with the situation.
Here are some news links you can read relating to the attack:
Update 9/13/2012 - It appears that this may not have been an attack after all. GoDaddy is saying that this was not an attack but a configuration error that cascaded through their routers taking their services off line for about six hours. Be it an attack or an accidental configuration issue makes no real difference to the end users that couldn't gain access to the web sites hosted on or registered with GoDaddy.
Although this was all very annoying, no personal information seems to have been accessed such as passwords, credit card numbers, addresses, phone numbers or alike. Personally, being a technical person, I feel GoDaddy handled this situation quite well. I am not happy that it happened or that our users were unable to get to the site. But the tech team at GoDaddy did a very good job at correcting the problems.