Đang chuẩn bị liên kết để tải về tài liệu:
Mission-Critical Security Planner When Hackers Won’t Take No for an Answer phần 2

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Đồng thời, ngành công nghiệp âm thanh phức tạp lái xe đã bị lu mờ bởi các thư viện âm thanh cực kỳ linh hoạt và mạnh mẽ của DirectX. Chương này là một đi chơi nhanh chóng thông qua phần DirectSound của DirectX Audio, với một chương trình nhỏ để chứng minh làm thế nào để sử dụng DirectSound để chơi các tập tin WAV | 28 Chapter 2 A senior management mandate and sponsorship are critical without them this team will die on the vine. Supportive senior management can grease the wheels meaning that the security team s recommendations will stand a much better chance of actually being implemented and supported throughout the company. An example of such a mandate would be this Our company is committed to maintaining shareholder value and protecting the interests and privacy of our customers and employees. Actively maintaining the security of our technology infrastructure is crucial to this commitment. The mandate could be followed up with specific performance goals the meeting of which are tied to the performance evaluations and to the compensation of company executives. After working to identify immediate high-impact concerns the team should begin the impact analysis process. The process when first performed in an organization will be confusing and difficult simply because most people will on their first attempt not have an intuitive feel for what it means to assign numbers to variables like denial of business. After working through four or five analyses looking at the numeric results for overall impact then weighing those results against their intuitive feel for what the real relative impact might be and revising accordingly any of their previously assigned values to reflect that the team will begin to feel comfortable assigning values to impact parameters. It s a somewhat self-correcting process the first few times. The results become more consistent as the team adapts to the process. In the beginning the team should meet at least once a week. Between meetings team members should collaborate as they work on their individual assignments. Soon the team will know how frequently to meet whether once a week or once a month based on the organization s needs. The team should increasingly alternate between impact analysis and worksheet development. Security worksheets are the backbone of the