Windows 10: Niemożliwa zmiana rozdzielczości ekranu

Beata Woźniak · Apr 28, 2023

Witam,ostatnio zainstalowałam Windows 11. Gdy próbuję zmienić rozdzielczość ekranu jest to niemozliwe, w ustawieniach pole jest wyszarzone. Poza tym mam problem z uruchamianiem gier. Proszę o pomoc.pozdrawiam, Beata

:)

Brink · Apr 28, 2023

CIS Microsoft 365 Foundations Benchmark now available

We’re excited to announce the availability of the Center for Internet Security’s (CIS) Microsoft 365 Foundations Benchmark—developed by CIS in partnership with Microsoft—to provide prescriptive guidance for establishing a secure baseline configuration for Microsoft 365. CIS is a nonprofit entity focused on developing global standards and recognized best practices for securing IT systems and data against the most pervasive attacks.

Microsoft 365 provides powerful online cloud services that enable collaboration, security, and compliance, mobility, intelligence, and analytics. Adopting cloud technologies requires a shared responsibility model for security, with Microsoft responsible for certain controls and the customer responsible for others, depending on the service delivery model chosen. To ensure that a customer’s cloud workloads are protected, it is important that they carefully consider and implement the appropriate architecture and enable the right set of configuration settings.

The CIS Microsoft 365 Foundations Benchmark is designed to assist organizations in establishing the foundation level of security for anyone adopting Microsoft 365. The benchmark should not be considered as an exhaustive list of all possible security configurations and architecture but as a starting point. Each organization must still evaluate their specific situation, workloads, and compliance requirements and tailor their environment accordingly.

The CIS benchmark contains two levels, each with slightly different technical specifications:

Level 1—Recommended minimum security settings that should be configured on any system and should cause little or no interruption of service or reduced functionality.

Level 2—Recommended security settings for highly secure environments and could result in some reduced functionality.

The CIS Microsoft 365 Security Benchmark is divided into the following sections:

[table][tr][td]Section[/td] [td]Description[/td] [td]# of recommended controls[/td] [/tr] [tr][td]Account/Authentication policies[/td] [td]Recommendations related to setting the appropriate account and authentication policies.[/td] [td]8[/td] [/tr] [tr][td]Application permissions[/td] [td]Recommendations related to the configuration of application permissions within Microsoft 365.[/td] [td]4[/td] [/tr] [tr][td]Data management[/td] [td]Recommendations for setting data management policies.[/td] [td]6[/td] [/tr] [tr][td]Email security/Exchange Online[/td] [td]Recommendations related to the configuration of Exchange Online and email security.[/td] [td]13[/td] [/tr] [tr][td]Auditing policies[/td] [td]Recommendations for setting auditing policies on your Microsoft 365 tenant.[/td] [td]14[/td] [/tr] [tr][td]Storage policies[/td] [td]Recommendations for securely configuring storage policies.[/td] [td]2[/td] [/tr] [tr][td]Mobile device management[/td] [td]Recommendations for managing devices connecting to Microsoft 365.[/td] [td]13[/td] [/tr] [tr][td]Total recommendations[/td] [td]60[/td] [/tr] [/table]

Each recommendation contains several sections, including a recommendation identification number, title, and description; level or profile applicability; rationale; instructions for auditing the control; remediation steps; impact of implementing the control; default value; and references. For example, the first control contained in the benchmark is under the Account/Authentication policies section and is titled: 1.1 (L1) Ensure multifactor authentication is enabled for all users in administrative roles (Scored).

A control is marked as “Scored” or “Not Scored” based on whether it can be programmatically tested. In this case, recommendation 1.1 can be audited leveraging the Microsoft Graph and PowerShell cmdlet. The specific steps for auditing the control are contained in the “Audit” section for this specific recommendation. This recommendation is listed as a Level 1 control because it is only applied to Microsoft 365 administrative users and would not have a company-wide impact or produce less functionality for users. The rationale for recommendation 1.1 is that Microsoft 365 administrative accounts need to be protected due to their powerful privileges and with Multiple Factor Authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk to the Azure tenant.

Download the benchmark and provide your feedback

The CIS Microsoft 365 Security Benchmark is freely available for download in PDF format on the CIS website. In the continuity of their mission, feedback provided by those entrenched in using and implementing the benchmarks provides us the opportunity for continuous improvement of our products. Feedback can be made visible to CIS by creating a discussion thread or ticket within the CIS Microsoft 365 Foundations Benchmark community. In addition, Microsoft has developed a set of Office 365 security guidelines and best practices for our customers to follow. These guides can be found in Office 365 Security and Compliance documentation.
Click to expand...

Source: Best practices for securely using Microsoft 365 - the CIS Microsoft 365 Foundations Benchmark now available - Microsoft Secure

Brink · Apr 28, 2023

CIS Microsoft 365 Foundations Benchmark now available

We’re excited to announce the availability of the Center for Internet Security’s (CIS) Microsoft 365 Foundations Benchmark—developed by CIS in partnership with Microsoft—to provide prescriptive guidance for establishing a secure baseline configuration for Microsoft 365. CIS is a nonprofit entity focused on developing global standards and recognized best practices for securing IT systems and data against the most pervasive attacks.

Microsoft 365 provides powerful online cloud services that enable collaboration, security, and compliance, mobility, intelligence, and analytics. Adopting cloud technologies requires a shared responsibility model for security, with Microsoft responsible for certain controls and the customer responsible for others, depending on the service delivery model chosen. To ensure that a customer’s cloud workloads are protected, it is important that they carefully consider and implement the appropriate architecture and enable the right set of configuration settings.

The CIS Microsoft 365 Foundations Benchmark is designed to assist organizations in establishing the foundation level of security for anyone adopting Microsoft 365. The benchmark should not be considered as an exhaustive list of all possible security configurations and architecture but as a starting point. Each organization must still evaluate their specific situation, workloads, and compliance requirements and tailor their environment accordingly.

The CIS benchmark contains two levels, each with slightly different technical specifications:

Level 1—Recommended minimum security settings that should be configured on any system and should cause little or no interruption of service or reduced functionality.

Level 2—Recommended security settings for highly secure environments and could result in some reduced functionality.

The CIS Microsoft 365 Security Benchmark is divided into the following sections:

[table][tr][td]Section[/td] [td]Description[/td] [td]# of recommended controls[/td] [/tr] [tr][td]Account/Authentication policies[/td] [td]Recommendations related to setting the appropriate account and authentication policies.[/td] [td]8[/td] [/tr] [tr][td]Application permissions[/td] [td]Recommendations related to the configuration of application permissions within Microsoft 365.[/td] [td]4[/td] [/tr] [tr][td]Data management[/td] [td]Recommendations for setting data management policies.[/td] [td]6[/td] [/tr] [tr][td]Email security/Exchange Online[/td] [td]Recommendations related to the configuration of Exchange Online and email security.[/td] [td]13[/td] [/tr] [tr][td]Auditing policies[/td] [td]Recommendations for setting auditing policies on your Microsoft 365 tenant.[/td] [td]14[/td] [/tr] [tr][td]Storage policies[/td] [td]Recommendations for securely configuring storage policies.[/td] [td]2[/td] [/tr] [tr][td]Mobile device management[/td] [td]Recommendations for managing devices connecting to Microsoft 365.[/td] [td]13[/td] [/tr] [tr][td]Total recommendations[/td] [td]60[/td] [/tr] [/table]

Each recommendation contains several sections, including a recommendation identification number, title, and description; level or profile applicability; rationale; instructions for auditing the control; remediation steps; impact of implementing the control; default value; and references. For example, the first control contained in the benchmark is under the Account/Authentication policies section and is titled: 1.1 (L1) Ensure multifactor authentication is enabled for all users in administrative roles (Scored).

A control is marked as “Scored” or “Not Scored” based on whether it can be programmatically tested. In this case, recommendation 1.1 can be audited leveraging the Microsoft Graph and PowerShell cmdlet. The specific steps for auditing the control are contained in the “Audit” section for this specific recommendation. This recommendation is listed as a Level 1 control because it is only applied to Microsoft 365 administrative users and would not have a company-wide impact or produce less functionality for users. The rationale for recommendation 1.1 is that Microsoft 365 administrative accounts need to be protected due to their powerful privileges and with Multiple Factor Authentication, an attacker would need to compromise at least two different authentication mechanisms, increasing the difficulty of compromise and thus reducing the risk to the Azure tenant.

Download the benchmark and provide your feedback

The CIS Microsoft 365 Security Benchmark is freely available for download in PDF format on the CIS website. In the continuity of their mission, feedback provided by those entrenched in using and implementing the benchmarks provides us the opportunity for continuous improvement of our products. Feedback can be made visible to CIS by creating a discussion thread or ticket within the CIS Microsoft 365 Foundations Benchmark community. In addition, Microsoft has developed a set of Office 365 security guidelines and best practices for our customers to follow. These guides can be found in Office 365 Security and Compliance documentation.
Click to expand...

Source: Best practices for securely using Microsoft 365 - the CIS Microsoft 365 Foundations Benchmark now available - Microsoft Secure

Brink · Apr 28, 2023

Announcing UI Tests in CI/CD for Desktop App Developers

For many years the ability to run UI tests in CI/CD has provided great value to web developers. This past Microsoft Build 2019 we were excited to announce desktop app developers can now also run UI tests in Azure DevOps! Desktop applications can now run automated UI tests in CI/CD on Azure DevOps using hosted or private agents, and setup is simple with a new Pipeline task.

Why UI tests in CI will help App Developers

Continuous Integration (CI) enables you to run automated tests of your application every time there’s a code change, and typically on servers so you’re not tying up desktop machines for testing. App developers have had the ability to run UI tests using WinAppDriver, and adding these tests to CI is important for a couple key reasons:

UI tests need interactive test machines. If you attempt to move the mouse, type on the keyboard, on a machine while a UI test is running, you will likely invalidate the test. This is because the tests perform automated user interactions in a way that does not differentiate from your physical actions.

CI is the right time to run UI Tests. There’s great value in having UI tests confirm if code changes break the user experience in your application. But equally important to having UI tests, is running them for every code change and pull request so you know exactly which commit broke the behavior. A key tenet of CI is to run every time the code changes.

How do UI tests work?

UI tests are automated tests designed to test an application by interacting with its UI in the same way a normal user would. These tests are different from unit/functional tests which test functional components of the application. A UI test typically involves going through an application in common scenarios just like a user would, verifying a user can accomplish common tasks. UI tests also typically record screenshots and often video of the test so the developer can review how the application appeared at various moments in the test.

What work was done to enable this?

For app developers to run UI tests in CI, the machine running the tests must be in an interactive state. This means the operating system has a logged in user and is listening for user input. You also need a test runner such as WinAppDriver on the test machine. Setting up a private agent in Azure DevOps with this configuration was possible, but it required significant manual configuration. Many customers requested enabling the hosted agent pool with a simple solution. The HostedVS2017 and HostedVS2019 agents are now updated with the following to enable UI tests in CI:

Support for interactive mode

Addition of WinAppDriver which executes the UI test commands

Both agents are included for free in the base Azure Pipelines plan.

In addition to the hosted agent additions there’s now a task in Azure Pipelines for easy addition of UI tests and added test configuration options. A preview of the WinAppDriver task is available today on the DevOps Marketplace. If you’re using the Classical Editor, search for “WinAppDriver” from the Add tasks menu:

For more information on the task, check out the updated CI with Azure Pipelines section on our Wiki.

Live Example: Microsoft Calculator

The recently open-sourced Microsoft Calculator project has UI Tests running in Azure DevOps as part of their CI. These tests are helping the Calculator Team catch PRs that break the user experience.

You can check out their DevOps CI/CD Pipeline fully integrated with the new WinAppDriver Task seen here:

Call to Action

Please take a look at Calculator and evaluate if adding UI tests in CI/CD will help your desktop application projects.

We’d love to hear from you. Please reach out on the WinAppDriver Issues Board on GitHub, or email L: [email protected]. For product announcements follow @mrhassanuz and @yosefdurr.
Click to expand...

Source: Announcing UI Tests in CI/CD for Desktop App Developers - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Windows 10: Niemożliwa zmiana rozdzielczości ekranu

Niemożliwa zmiana rozdzielczości ekranu

Niemożliwa zmiana rozdzielczości ekranu

Niemożliwa zmiana rozdzielczości ekranu

Niemożliwa zmiana rozdzielczości ekranu - Similar Threads - Niemożliwa zmiana rozdzielczości

Migotanie ekranu

Migotanie ekranu

Niemożliwa zmiana rozdzielczości ekranu

Przywrócenie niezapisanego pliku z nagrywania ekranu windows

Przywrócenie niezapisanego pliku z nagrywania ekranu windows